| 2 | Approval of the agenda | |
|---|---|---|
| R4-2104436 | RAN4#98-e Meeting Report | ETSI MCC |
| R4-2105235 | RAN4 Meeting Efficiency Improvements | RAN4 Chair (Apple) |
| R4-2107131 | Agenda for RAN4#98-bis-e | RAN4 Chair (Apple) |
| R4-2107132 | RAN4#98-bis-e E-meeting Arrangements and Guidelines | RAN4 Chair (Apple) |
| 4 | Letters / reports from other groups / meetings | |
| R4-2104438 | Spurious emission limits for AAS BS in 6.425 – 7.125 GHz and 10-10.5 GHz | CEPT ECC PT1 |
| R4-2104440 | Reply LS on CSI-RS only beam correspondence | RAN1 |
| R4-2104442 | Reply LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN1 |
| R4-2104443 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#104-e | RAN1 |
| R4-2104444 | Reply LS on measuring CSI-RS during SCell activation | RAN1 |
| R4-2104445 | Reply LS on TCI state indication at Direct SCell activation | RAN1 |
| R4-2104446 | Reply LS on SL switching priority | RAN1 |
| R4-2104447 | LS on uplink Tx switching | RAN1 |
| R4-2104448 | LS on Introduction of DL 1024QAM for NR | RAN1 |
| R4-2104449 | LS on the maximum/minimum channel bandwidth and channelization for NR operation in 52.6 to 71 GHz | RAN1 |
| R4-2104450 | LS on Half-duplex FDD switching time for RedCap UE | RAN1 |
| R4-2104451 | LS on beam switching gap for 60 GHz band | RAN1 |
| R4-2104452 | LS on Agreements Pertaining to L1/L2-Centric Inter-Cell Mobility | RAN1 |
| R4-2104453 | LS on UE transmit timing error | RAN1 |
| R4-2104455 | LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN1 |
| R4-2104462 | LS on NTN UL time and frequency synchronization requirements | RAN1 |
| R4-2104463 | Reply LS on nominal channel spacing calculation for two carriers at band n41 with 40MHz and 80MHz channel bandwidths | RAN5 |
| R4-2104470 | Clarification on exception requirements for Intermodulation due to Dual uplink (IMD) | RAN5 |
| R4-2104471 | LS On minimum requirements for Transmit ON/OFF time mask in UL MIMO FR1 | RAN5 |
| R4-2104472 | Reply LS on questions to RAN WGs on dual Radio UE (2Rx/2Tx or 2Rx/1Tx) support for simultaneous communication with both SNPN and PLMN | RAN2 |
| R4-2104473 | Reply LS on Use of Inclusive Language in 3GPP | RAN2 |
| R4-2104474 | LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state | RAN2 |
| R4-2104475 | Reply LS on DC location reporting for intra-band UL CA | RAN2 |
| R4-2104476 | Reply LS on Rel-16 mandatory RRM requirements | RAN2 |
| R4-2104477 | LS Reply on RRC based BWP switch | RAN2 |
| R4-2104478 | Reply LS on simultaneous Rx/Tx capability | RAN2 |
| R4-2105105 | FREQUENCY ARRANGEMENTS FOR IMT IN THE BAND 470 – 703 MHZ | AWG-27 |
| 5.1 | NR-based access to unlicensed spectrum | |
| R4-2106167 | Big draftCR for NR-U BS conducted conformance testing in TS 38.141-1 | Ericsson |
| R4-2106168 | Big draftCR for NR-U BS radiated conformance testing in TS 38.141-2 | Nokia, Nokia Shanghai Bell |
| R4-2106173 | Way Forward on NR-U UE demodulation requirements | Qualcomm |
| 5.1.1 | BS conformance testing | |
| R4-2105972 | Email discussion summary for [98bise][301] NR_unlic_BS_Conformance | Moderator (ZTE Corporation) |
| R4-2106132 | Email discussion summary for [98bise][301] NR_unlic_BS_Conformance | Moderator (ZTE Corporation) |
| 5.1.1.1 | General | |
| R4-2106002 | Draft CR to TS 38.141-1: introduction of NR-U BS | ZTE Corporation |
| R4-2106005 | WF on NR-U BS wideband operation testing | Nokia |
| R4-2106163 | Draft CR to 37.141: Introduction of NR-U co-existence requirements | Nokia, Nokia Shanghai Bell |
| R4-2106308 | Discussion on test configurations for wideband NR-U operation | Nokia, Nokia Shanghai Bell |
| R4-2106311 | Draft CR to TS 38.141-1 – Test configurations for NR-U BS conformance tests | Nokia, Nokia Shanghai Bell |
| R4-2106312 | Draft CR to TS 38.141-2 – Test configurations for NR-U BS conformance tests | Nokia, Nokia Shanghai Bell |
| R4-2106474 | NR-U measurement uncertainty for BS | Keysight Technologies UK Ltd |
| R4-2106477 | MU for unlicensed band n46 and n96 | Huawei, HiSilicon |
| R4-2106605 | Draft CR to TS 38.141-1: introduction of NR-U BS | ZTE Corporation |
| R4-2106606 | Draft CR to TS 36.141: introduction of NR-U BS | ZTE Corporation |
| R4-2107037 | Draft CR to 37.141: Introduction of NR-U co-existence requirements | Nokia, Nokia Shanghai Bell |
| 5.1.1.2 | Transmitter characteristics | |
| R4-2104464 | TS 37.145-2: Tx spurious limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2104465 | TS 37.145-2: Tx spurious limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2104466 | TS 38.141-2: Tx spurious limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2104467 | TS 38.141-2: Tx spurious limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2104468 | TS 37.145-2: Rx blocking limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2104469 | TS 37.145-2: RX blocking limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2104652 | TS 37.145-2: Tx spurious limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2104653 | TS 38.141-2: Tx spurious limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2104654 | TS 37.145-2: Rx blocking limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2106003 | TS 38.141-2: Tx spurious limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2106004 | TS 37.145-2: Tx spurious limits for co-existence and co-location with of NR-based access to unlicensed spectrum (NR-U) | Ericsson |
| R4-2106310 | Draft CR to TS 37.107 With NR-U intorduction for performance part | Nokia, Nokia Shanghai Bell |
| R4-2106478 | draft CR to 38.141-1 TX test system uncertainty | Huawei, HiSilicon |
| 5.1.1.3 | Receiver characteristics | |
| R4-2106320 | On NR-U MUs and TTs for band n46 and n96 | Nokia, Nokia Shanghai Bell |
| R4-2106479 | draft CR to 38.141-1 RX test system uncertainty | Huawei, HiSilicon |
| 5.1.2 | RRM core requirements maintenance (38.133) | |
| R4-2105671 | Email discussion summary for [98-bis-e][201] NR_unlic_RRM_1 | Moderator (Ericsson) |
| R4-2105699 | LS on SCell activation requirements for NR-U | Nokia |
| R4-2105700 | WF on NR-U RRM Core Requirements | Ericsson |
| R4-2105803 | Email discussion summary for [98-bis-e][201] NR_unlic_RRM_1 | Moderator (Ericsson) |
| 5.1.2.1 | General | |
| R4-2104430 | On terminology updates for measurements in NR-U | ZTE Corporation |
| R4-2105706 | Terminology updates for NR-U in 38.133 | Ericsson |
| R4-2105707 | Terminology updates for NR-U in 36.133 | Ericsson |
| R4-2106840 | Terminology updates for NR-U in 38.133 | Ericsson |
| R4-2106841 | Terminology updates for NR-U in 36.133 | Ericsson |
| R4-2106959 | Discussion on NR-U terminology clarification | Huawei, HiSilicon |
| R4-2107087 | Discussion on terminology for NR-U RRM requirements | MediaTek inc. |
| 5.1.2.2 | RRC connection mobility control | |
| R4-2106960 | Discussion on SI reading with LBT | Huawei, HiSilicon |
| R4-2106961 | Draft CR on SI acquisition for RRC connection mobility control for NR-U TS 36.133 | Huawei, HiSilicon |
| R4-2106962 | Draft CR on SI acquisition for RRC connection mobility control for NR-U TS 38.133 | Huawei, HiSilicon |
| 5.1.2.3 | SCell activation/deactivation (delay and interruption) | |
| R4-2104826 | On SCell activation requirement for NR-U | Apple |
| R4-2104827 | CR on SCell activation requirement for NR-U R16 | Apple |
| R4-2104828 | CR on SCell activation requirement for NR-U R17 | Apple |
| R4-2105005 | Draft CR on SCell activation requirement for NR-U R16 | Apple |
| R4-2105701 | Updates in SCell activation in NR-U | Ericsson |
| R4-2105702 | Draft CR on SCell activation requirement for NR-U R16 | Apple |
| R4-2105708 | Draft CR on SCell activation requirements for NR-U | Huawei, HiSilicon |
| R4-2106573 | SCell (de)activation requirement applicability when sCellDeactivationTimer is not configured | Nokia, Nokia Shanghai Bell |
| R4-2106844 | On remaining issues for SCell activation in NR-U | Ericsson |
| R4-2106845 | Updates in SCell activation in NR-U | Ericsson |
| R4-2106914 | On SCell activation in NR-U | ZTE Corporation |
| R4-2106963 | Discussion on SCell activation and deactivation requirements for NR-U | Huawei, HiSilicon |
| R4-2106964 | Draft CR on SCell activation requirements for NR-U | Huawei, HiSilicon |
| R4-2107088 | Discussion on Scell activation requirement in NR-U for NR-U | MediaTek inc. |
| R4-2107358 | Interruptions during SCell activation in NR-U | Qualcomm Incorporated |
| 5.1.2.4 | Active TCI state switching | |
| R4-2106965 | Draft CR on Active TCI state switching for NR-U | Huawei, HiSilicon |
| 5.1.2.5 | RLM | |
| R4-2105703 | Draft CR on RLM requirements for NR-U | Huawei, HiSilicon |
| R4-2106966 | Draft CR on RLM requirements for NR-U | Huawei, HiSilicon |
| 5.1.2.6 | Beam management | |
| R4-2106967 | Draft CR on Beam management requirements for NR-U | Huawei, HiSilicon |
| 5.1.2.7 | Measurement requirements | |
| R4-2105704 | Draft CR on measurement requirements for NR-U | Huawei, HiSilicon |
| R4-2106968 | Draft CR on measurement requirements for NR-U | Huawei, HiSilicon |
| 5.1.2.8 | Measurement capability and reporting criteria | |
| R4-2105705 | Draft CR on CSSF updating for NR-U | Huawei, HiSilicon |
| R4-2106969 | Draft CR on CSSF updating for NR-U | Huawei, HiSilicon |
| 5.1.2.9 | Timing | |
| R4-2104823 | On reference cell availability for NR-U | Apple |
| R4-2104824 | CR on reference cell availability for NR-U R16 | Apple |
| R4-2104825 | CR on reference cell availability for NR-U R17 | Apple |
| R4-2105004 | Draft CR on reference cell availability for NR-U R16 | Apple |
| R4-2106970 | Discussion on timing requirements for NR-U | Huawei, HiSilicon |
| R4-2106971 | Draft CR on timing requirements for NR-U | Huawei, HiSilicon |
| R4-2107089 | Discussion on UE Transmit Timing for NR-U | MediaTek inc. |
| R4-2107138 | Further analysis of UE transmit timing under DL LBT failure in reference cell | Ericsson |
| R4-2107359 | Reference cell under CCA for UE transmit timings | Qualcomm Incorporated |
| 5.1.2.10 | Other requirements | |
| R4-2106839 | On SSB availability to meet NR-U requirements in DRX | Ericsson |
| R4-2106842 | NR-U bands | Ericsson |
| R4-2106972 | Draft CR on core requirements maintenance of IDLE mode inter-RAT measurement for NR-U TS 36.133 | Huawei, HiSilicon |
| R4-2106973 | Draft CR on PSCell Addition requirements for NR-U | Huawei, HiSilicon |
| R4-2106974 | Draft CR on SI acquisition for paging interruption for NR-U | Huawei, HiSilicon |
| 5.1.3 | RRM perf. requirements (38.133) | |
| R4-2105672 | Email discussion summary for [98-bis-e][202] NR_unlic_RRM 2 | Moderator (Nokia, Nokia Shanghai Bell) |
| R4-2105709 | WF on general test configurations for NR-U RRM performance requirements | Nokia |
| R4-2105710 | WF on LBT models for NR-U RRM performance requirements | Qualcomm |
| R4-2105804 | Email discussion summary: [98-bis-e][202] NR_unlic_RRM_2 | Moderator (Nokia) |
| R4-2105834 | Draft CR of test case configurations for NR-U | Huawei, HiSilicon |
| 5.1.3.1 | General | |
| R4-2105711 | Updated test case list for NR-U | Ericsson |
| R4-2105712 | Draft Big CR: Introduction of Rel-16 NR-U RRM performance requirements | Ericsson |
| R4-2106846 | Draft Big CR: Introduction of Rel-16 NR-U RRM performance requirements | Ericsson |
| R4-2106848 | Updated test case list for NR-U | Ericsson |
| R4-2107360 | SI Reading time during RRC Mobility Control in NR-U | Qualcomm Incorporated |
| R4-2107362 | Updated NR-U RRM Performance Work Plan | Qualcomm Incorporated |
| 5.1.3.2 | Measurement accuracy requirements | |
| R4-2106843 | NR-U conditions | Ericsson |
| R4-2106847 | NR-U accuracy requirements | Ericsson |
| R4-2106879 | DraftCR 36.133 Correction of accuracy requirements for NR-U bands | Ericsson |
| R4-2106975 | Draft CR on inter-RAT NR measurement accuracy requirements | Huawei, HiSilicon |
| 5.1.3.3.1 | General | |
| R4-2104431 | Configurations for NR-U RRM test cases | ZTE Corporation |
| R4-2106357 | Discussion on RRM test cases in NR-U | MediaTek inc. |
| R4-2106574 | On remaining details of NR-U RRM test configurations | Nokia, Nokia Shanghai Bell |
| R4-2106580 | Draft CR on DL CCA model for NR-U | Nokia, Nokia Shanghai Bell |
| R4-2106849 | On CCA model in NR-U test cases | Ericsson |
| R4-2106850 | CCA model in NR-U test cases | Ericsson |
| R4-2106871 | Common test parameters for NR-U RRM tests | Ericsson |
| R4-2106873 | Draft CR: Update of RMC for NR-U test cases | Ericsson |
| R4-2106976 | Discussion on RRM performance testing for NR-U | Huawei, HiSilicon |
| R4-2106977 | Draft CR of test case configurations for NR-U | Huawei, HiSilicon |
| R4-2107361 | CCA models in NR-U | Qualcomm Incorporated |
| 5.1.3.3.2 | RRC IDLE cell re-selection | |
| R4-2105715 | Introduction of NR-U cell reselection tests | Ericsson |
| R4-2106853 | Discussions on cell reselection test cases for NR-U | Ericsson |
| R4-2106854 | Introduction of NR-U cell reselection tests | Ericsson |
| 5.1.3.3.3 | HO (delay and interruptions) | |
| R4-2105716 | Draft TC NR-U handover test cases | Nokia, Nokia Shanghai Bell |
| R4-2105717 | Introduction of NR-U handover tests | Ericsson |
| R4-2105718 | Draft CR of test cases for HO delay and interruption for NR-U | Huawei, HiSilicon |
| R4-2106575 | Discussion about HO test cases with shared core requirements | Nokia, Nokia Shanghai Bell |
| R4-2106576 | Draft TC NR-U handover test cases | Nokia, Nokia Shanghai Bell |
| R4-2106855 | Discussions on handover test cases for NR-U | Ericsson |
| R4-2106856 | Introduction of NR-U handover tests | Ericsson |
| R4-2106978 | Draft CR of test cases for HO delay and interruption for NR-U | Huawei, HiSilicon |
| 5.1.3.3.4 | RRC Re-establishment | |
| R4-2104432 | Test cases for RRC re-establishment in NR-U | ZTE Corporation |
| R4-2106577 | Draft TC RRC re-establishment with CCA | Nokia, Nokia Shanghai Bell |
| R4-2107141 | RRC re-establishment tests for NR-U | Ericsson |
| R4-2107142 | RRC re-establishment tests for NR-U in 38.133 | Ericsson |
| 5.1.3.3.5 | RRC Connection Release with Redirection | |
| R4-2104433 | Test cases for RRC release with re-direction in NR-U | ZTE Corporation |
| R4-2105719 | Draft CR on test cases for RRC release with redirection for NR-U | Huawei, HiSilicon |
| R4-2105720 | RRC connection release with re-direction from NR to NR-U test in 38.133 | Ericsson |
| R4-2106979 | Draft CR on test cases for RRC release with redirection for NR-U | Huawei, HiSilicon |
| R4-2107143 | RRC connetion release with re-direction from NR to NR-U test | Ericsson |
| R4-2107144 | RRC connetion release with re-direction from NR to NR-U test in 38.133 | Ericsson |
| 5.1.3.3.6 | Random access | |
| R4-2105721 | Draft CR: Random access procedure test cases for NR-U | Ericsson, Nokia |
| R4-2106579 | Draft CR NR-U RRM random access performance requirements | Nokia, Nokia Shanghai Bell |
| R4-2106876 | Test cases on random access for NR-U | Ericsson |
| R4-2106877 | Draft CR: Random access procedure test cases for NR-U | Ericsson |
| 5.1.3.3.7 | Timing (transmit timing and TA) | |
| R4-2104434 | Test cases for timing in NR-U | ZTE Corporation |
| R4-2106980 | Discussion on test cases for timing requirements for NR-U | Huawei, HiSilicon |
| 5.1.3.3.8 | BWP switching delay and interruptions | |
| R4-2104435 | Test cases for BWP switching in NR-U | ZTE Corporation |
| R4-2105722 | Test cases on BWP switching for NR-U SA in TS 38.133 | Ericsson |
| R4-2107145 | Test cases on BWP switching for NR-U SA | Ericsson |
| R4-2107146 | Test cases on BWP switching for NR-U SA in TS 38.133 | Ericsson |
| 5.1.3.3.9 | PSCell addition/release (delay and interruption) | |
| R4-2105723 | Draft CR of test cases for PSCell addition and release for NR-U | Huawei, HiSilicon |
| R4-2106981 | Draft CR of test cases for PSCell addition and release for NR-U | Huawei, HiSilicon |
| 5.1.3.3.13 | Beam management (BFD and link recovery) | |
| R4-2105724 | Draft CR: Update of beam management test cases for NR-U | Ericsson |
| R4-2106874 | Test cases on link recovery and L1-RSRP reporting for NR-U | Ericsson |
| R4-2106875 | Draft CR: Update of beam management test cases for NR-U | Ericsson |
| 5.1.3.3.14 | SS-RSRP/SS-RSRQ/SS-SINR/L1-RSRP measurement procedure (intra-frequency, inter-frequency, inter-RAT) | |
| R4-2105725 | Draft CR on test cases for inter-RAT measurement for NR-U | Huawei, HiSilicon |
| R4-2106578 | Draft TC NR-U inter-frequency measurements | Nokia, Nokia Shanghai Bell |
| R4-2106982 | Draft CR on test cases for inter-RAT measurement for NR-U | Huawei, HiSilicon |
| 5.1.3.3.17 | SS-RSRP/SS-RSRQ/SS-SINR/L1-RSRP measurement accuracy (intra-frequency, inter-frequency, inter-RAT) | |
| R4-2105726 | Introduction of test cases for L1-RSRP measurement accuracy with CCA serving cel | MediaTek |
| R4-2106358 | Introduction of test cases for NR-U inter-frequency SS-RSRP measurement accuracy | MediaTek inc. |
| R4-2106359 | Introduction of test cases for L1-RSRP measurement accuracy with CCA serving cell | MediaTek inc. |
| R4-2106983 | Draft CR on test cases for intra-frequency measurement accuracy for NR-U | Huawei, HiSilicon |
| 5.1.3.3.18 | RSSI/CO measurement accuracy (intra-frequency, inter-frequency, inter-RAT) | |
| R4-2104829 | On RSSI and CO testing in NR-U | Apple |
| R4-2104830 | Test cases for RSSI and CO measurement accuracy in NR-U R16 | Apple |
| R4-2105727 | Draft CR on test cases for intra-frequency measurement accuracy for NR-U | Huawei, HiSilicon |
| R4-2105728 | Test cases for RSSI and CO measurement accuracy in NR-U R16 | Apple |
| 5.1.3.3.20 | Other | |
| R4-2105714 | Applicability rules for legacy NR tests for NR-U in 38.133 | Ericsson |
| R4-2106984 | Discussion on test cases for TCI switching for NR-U | Huawei, HiSilicon |
| R4-2107139 | Applicability rules for legacy NR tests for NR-U | Ericsson |
| R4-2107140 | Applicability rules for legacy NR tests for NR-U in 38.133 | Ericsson |
| 5.1.4.1 | General | |
| R4-2104544 | Discussion on NR-U general issue for UE and CSI demodulation | Ericsson |
| R4-2105986 | Email disc+B1588:R1588ussion summary for [98-bis-e][315]NR_unlic_Demod_UE | Qualcomm |
| R4-2106007 | Way Forward on NR-U UE demodulation requirements | Qualcomm |
| R4-2106008 | Updated Work Plan for NR-U Demod | Qualcomm Incorporated |
| R4-2106010 | WF on NR-U BS demodulation requirements | Huawei |
| R4-2106133 | Email disc+B1588:R1588ussion summary for [98-bis-e][315]NR_unlic_Demod_UE | Qualcomm |
| R4-2106166 | Big draftCR for NR-U BS demodulation requirements in TS 38.104 | Huawei, HiSilicon |
| R4-2106469 | Updated Work Plan for NR-U Demod | Qualcomm Incorporated |
| R4-2106470 | Discussion on NR-U UE Demodulation Requirements | Qualcomm Incorporated |
| 5.1.4.2 | UE demodulation requirements | |
| R4-2104545 | Discussion on NR-U UE demodulation | Ericsson |
| R4-2104546 | Simulation result for NR-U PDSCH demodulation | Ericsson |
| R4-2104838 | Discussion on UE demodulation requirements in NR-U | Apple |
| R4-2104839 | Simulation results for PDSCH demodulation requirements in NR-U | Apple |
| R4-2104840 | Summary of simulation results for NR-U UE Demod | Apple |
| R4-2106471 | Simulation Results for NR-U PDSCH UE Demodulation Tests | Qualcomm Incorporated |
| R4-2106507 | NR-U PDSCH simulation results | Intel Corporation |
| R4-2106783 | Simulation results on NR-U PDSCH requirements | Huawei, HiSilicon |
| R4-2106784 | Discussion on UE performance requirements for Rel-16 NR-U | Huawei, HiSilicon |
| R4-2107091 | Discussion on PDSCH requirements for NR-U | MediaTek inc. |
| 5.1.4.3 | CSI requirements | |
| R4-2104547 | Discussion on NR-U CSI demodulation | Ericsson |
| R4-2104841 | On CQI reporting requirements in NR-U | Apple |
| R4-2106472 | Discussion on NR-U CQI Performance Tests | Qualcomm Incorporated |
| R4-2106785 | Discussions on NR-U CQI requirements | Huawei, HiSilicon |
| R4-2107090 | Discussion on CQI requirements for NR-U | MediaTek inc. |
| 5.1.4.4 | BS demodulation requirements | |
| R4-2105987 | Email disc+B1589:V1589ussion summary for [98-bis-e][316] NR_unlic_Demod_BS | Moderator (Huawei, HiSilicon) |
| R4-2106134 | Email disc+B1589:V1589ussion summary for [98-bis-e][316] NR_unlic_Demod_BS | Moderator (Huawei, HiSilicon) |
| 5.1.4.4.1 | General | |
| R4-2104619 | DraftCR on NR-U BS-demod applicability rules (38.141-1) | Nokia, Nokia Shanghai Bell |
| R4-2104620 | DraftCR on NR-U BS-demod applicability rules (38.141-2) | Nokia, Nokia Shanghai Bell |
| R4-2106011 | DraftCR on NR-U BS-demod applicability rules (38.141-1) | Nokia, Nokia Shanghai Bell |
| R4-2106012 | DraftCR on NR-U BS-demod applicability rules (38.141-2) | Nokia, Nokia Shanghai Bell |
| R4-2106786 | Summary of simulation results for NR-U BS performance requirements | Huawei, HiSilicon |
| 5.1.4.4.2 | PUSCH requirements | |
| R4-2104548 | Discussion on NR-U PUSCH demodulation | Ericsson |
| R4-2104549 | Simulation result for NR-U PUSCH demodulation | Ericsson |
| R4-2104621 | PUSCH Demodulation performance requirements for operation in unlicensed bands | Nokia, Nokia Shanghai Bell |
| R4-2104622 | NR-U PUSCH simulation results | Nokia, Nokia Shanghai Bell |
| R4-2106013 | Draft CR: Introduction of conducted and radiated performance requrements for PUSCH with interlace allocation in TS 38.104 | Huawei, HiSilicon |
| R4-2106014 | Draft CR: Introduction of FRC tables for PUSCH performance requirements with interlace allocation in TS 38.104 | Huawei, HiSilicon |
| R4-2106015 | Draft CR: Introduction of conducted conformance testing for PUSCH with interlace allocation in TS 38.141-1 | Huawei, HiSilicon |
| R4-2106016 | Draft CR: Introduction of FRC tables for conducted conformance testing for PUSCH with interlace allocation in TS 38.141-1 | Huawei, HiSilicon |
| R4-2106017 | Draft CR: Introduction of radiated conformance testing for PUSCH with interlace allocation in TS 38.141-2 | Huawei, HiSilicon |
| R4-2106018 | Draft CR: Introduction of FRC tables for radiated conformance testing for PUSCH with interlace allocation in TS 38.141-2 | Huawei, HiSilicon |
| R4-2106508 | NR-U PUSCH simulation results | Intel Corporation |
| R4-2106787 | Simulation results on NR-U PUSCH performance requirements | Huawei, HiSilicon |
| R4-2106788 | Discussions on NR-U PUSCH performance requirements | Huawei, HiSilicon |
| R4-2106789 | Draft CR: Introduction of conducted and radiated performance requrements for PUSCH with interlace allocation in TS 38.104 | Huawei, HiSilicon |
| R4-2106790 | Draft CR: Introduction of FRC tables for PUSCH performance requirements with interlace allocation in TS 38.104 | Huawei, HiSilicon |
| R4-2106791 | Draft CR: Introduction of conducted conformance testing for PUSCH with interlace allocation in TS 38.141-1 | Huawei, HiSilicon |
| R4-2106792 | Draft CR: Introduction of FRC tables for conducted conformance testing for PUSCH with interlace allocation in TS 38.141-1 | Huawei, HiSilicon |
| R4-2106793 | Draft CR: Introduction of radiated conformance testing for PUSCH with interlace allocation in TS 38.141-2 | Huawei, HiSilicon |
| R4-2106794 | Draft CR: Introduction of FRC tables for radiated conformance testing for PUSCH with interlace allocation in TS 38.141-2 | Huawei, HiSilicon |
| 5.1.4.4.3 | PUCCH requirements | |
| R4-2104550 | Discussion on NR-U PUCCH demodulation | Ericsson |
| R4-2104551 | Simulation result for NR-U PUCCH demodulation | Ericsson |
| R4-2104554 | draft CR for TS38.104 adding NR-U PUCCH ePF0 and ePF1 requirements | Ericsson |
| R4-2104555 | draft CR for TS38.141-1 adding NR-U PUCCH ePF0 and ePF1 requirements | Ericsson |
| R4-2104556 | draft CR for TS38.141-2 adding NR-U PUCCH ePF0 and ePF1 requirements | Ericsson |
| R4-2104623 | PUCCH Demodulation performance requirements for operation in unlicensed bands | Nokia, Nokia Shanghai Bell |
| R4-2104624 | NR-U PUCCH simulation results | Nokia, Nokia Shanghai Bell |
| R4-2105032 | draft CR on interlaced PUCCH performance requirement for TS 38.104 | Samsung |
| R4-2105033 | draft CR on interlaced PUCCH performance requirement for TS 38.141-1 | Samsung |
| R4-2105034 | draft CR on interlaced PUCCH performance requirement for TS 38.141-2 | Samsung |
| R4-2106019 | draft CR for TS38.104 adding NR-U PUCCH ePF0 and ePF1 requirements | Ericsson |
| R4-2106020 | draft CR for TS38.141-1 adding NR-U PUCCH ePF0 and ePF1 requirements | Ericsson |
| R4-2106021 | draft CR for TS38.141-2 adding NR-U PUCCH ePF0 and ePF1 requirements | Ericsson |
| R4-2106022 | draft CR on interlaced PUCCH performance requirement for TS 38.104 | Samsung |
| R4-2106023 | draft CR on interlaced PUCCH performance requirement for TS 38.141-1 | Samsung |
| R4-2106024 | draft CR on interlaced PUCCH performance requirement for TS 38.141-2 | Samsung |
| R4-2106795 | Simulation results on NR-U PUCCH performance requirements | Huawei, HiSilicon |
| 5.1.4.4.4 | PRACH requirements | |
| R4-2104552 | Discussion on NR-U PRACH demodulation | Ericsson |
| R4-2104553 | Simulation result for NR-U PRACH demodulation | Ericsson |
| R4-2104625 | PRACH Demodulation performance requirements for operation in unlicensed bands | Nokia, Nokia Shanghai Bell |
| R4-2104626 | NR-U PRACH simulation results | Nokia, Nokia Shanghai Bell |
| R4-2104627 | DraftCR NR-U BS demod PRACH performance requirements 38.104 | Nokia, Nokia Shanghai Bell |
| R4-2104628 | DraftCR NR-U BS demod PRACH conducted performance requirements 38.141-1 | Nokia, Nokia Shanghai Bell |
| R4-2104629 | DraftCR NR-U BS demod PRACH radiated performance requirements 38.141-2 | Nokia, Nokia Shanghai Bell |
| R4-2106025 | DraftCR NR-U BS demod PRACH performance requirements 38.104 | Nokia, Nokia Shanghai Bell |
| R4-2106026 | DraftCR NR-U BS demod PRACH conducted performance requirements 38.141-1 | Nokia, Nokia Shanghai Bell |
| R4-2106027 | DraftCR NR-U BS demod PRACH radiated performance requirements 38.141-2 | Nokia, Nokia Shanghai Bell |
| R4-2106509 | NR-U PRACH simulation results | Intel Corporation |
| R4-2106796 | Simulation results on NR-U PRACH performance requirements | Huawei, HiSilicon |
| 5.2.1.1 | General | |
| R4-2104999 | Summary of simulation results for V2X demodulation requirements | LG Electronics Inc. |
| R4-2105002 | Discussion on contents and table format for V2X demodulation specification | LG Electronics Inc. |
| R4-2105988 | Email discussion summary for [98-bis-e][317] V2X_Demod_Part1 | Moderator (LG Electronics) |
| R4-2106030 | Draft CR on General section of NR V2X requirements | Intel Corporation |
| R4-2106161 | Draft Big CR: Introduction of Rel-16 NR V2X demodulation performance requirements | LGE |
| R4-2106415 | Discussion on NR V2X requirements structure | Intel Corporation |
| R4-2106416 | Draft CR on General section of NR V2X requirements | Intel Corporation |
| 5.2.1.2 | Single link test | |
| R4-2104992 | Simulation results for NR V2X single link tests | LG Electronics Inc. |
| R4-2106028 | WF on remaining issues for single link tests for NR V2X demodulation performance | LGE |
| R4-2106029 | Draft CR for 38.101-4: Introduce PSBCH performance requirements for NR V2X | CATT, GOHIGH |
| R4-2106135 | Email discussion summary for [98-bis-e][317] V2X_Demod_Part1 | LGE |
| R4-2107219 | PSBCH simulation results discussion | Qualcomm, Inc. |
| 5.2.1.2.1 | PSSCH demodulation test | |
| R4-2104573 | Simulation results for NR V2X PSSCH test case | MediaTek inc. |
| R4-2104773 | Simulation results of NR V2X single link demodulation test | CATT |
| R4-2104995 | Draft CR for PSSCH demodulation requirements for NR V2X | LG Electronics Inc. |
| R4-2106031 | Draft CR for PSSCH demodulation requirements for NR V2X | LGE |
| R4-2106417 | Simulation results for NR V2X Single Link PSSCH requirements | Intel Corporation |
| R4-2106797 | Simulation results on PSSCH requirements | Huawei, HiSilicon |
| 5.2.1.2.2 | PSCCH demodulation test | |
| R4-2104574 | Simulation results for NR V2X PSCCH test case | MediaTek inc. |
| R4-2106032 | Draft CR on NR V2X Single Link PSCCH requirements | Intel Corporation |
| R4-2106418 | Simulation results for NR V2X Single Link PSCCH requirements | Intel Corporation |
| R4-2106419 | Draft CR on NR V2X Single Link PSCCH requirements | Intel Corporation |
| R4-2106798 | Simulation results on PSCCH requirements | Huawei, HiSilicon |
| 5.2.1.2.3 | PSBCH demodulation test | |
| R4-2104575 | Simulation results for NR V2X PSBCH test case | MediaTek inc. |
| R4-2106420 | Simulation results for NR V2X Single Link PSBCH requirements | Intel Corporation |
| R4-2106799 | Simulation results on PSBCH requirements | Huawei, HiSilicon |
| 5.2.1.2.4 | PSFCH demodulation test | |
| R4-2104576 | CR on NR V2X PSFCH demodulation requirements | MediaTek inc. |
| R4-2106033 | CR on NR V2X PSFCH demodulation requirements | MediaTek |
| R4-2106421 | Simulation results for NR V2X Single Link PSFCH requirements | Intel Corporation |
| R4-2106800 | Simulation results on PSFCH requirements | Huawei, HiSilicon |
| 5.2.1.3 | Multiple link test | |
| R4-2104902 | V2X multiple link demod discussion | Qualcomm, Inc. |
| R4-2104998 | Simulation results for NR V2X multiple link tests | LG Electronics Inc. |
| R4-2105989 | Email discussion summary for [98-bis-e][318] V2X_Demod_Part2 | Moderator (Intel Corporation) |
| R4-2106034 | WF on multiple link tests for NR V2X demodulation performance | Intel Corporation |
| R4-2106035 | Updated simulation assumptions for NR V2X multiple link test case | Huawei |
| R4-2106136 | Email discussion summary for [98-bis-e][318] V2X_Demod_Part2 | Moderator (Intel) |
| R4-2106160 | Simulation results for NR V2X multiple link tests | LGE |
| R4-2106425 | Summary of NR V2X Multiple link simulation results | Intel Corporation |
| 5.2.1.3.1 | Power imbalance requirement | |
| R4-2104774 | Simulation results of NR V2X multiple link demodulation test | CATT |
| R4-2106036 | CR for 38.101-4: Introduction of power imbalance requirements for NR V2X. | Huawei, HiSilicon |
| R4-2106422 | Simulation results for NR V2X Multiple Link Power Imbalance requirements | Intel Corporation |
| R4-2106801 | Simulation results on NR V2X power imbalance test | Huawei, HiSilicon |
| R4-2106802 | CR for 38.101-4: Introduction of power imbalance requirements for NR V2X. | Huawei, HiSilicon |
| 5.2.1.3.2 | HARQ soft buffer combing test | |
| R4-2104903 | CR: HARQ buffer TC | Qualcomm, Inc. |
| R4-2106037 | CR: HARQ buffer TC | Qualcomm |
| R4-2106423 | Discussion on NR V2X Multiple Link HARQ soft buffer combing requirements | Intel Corporation |
| R4-2106803 | Discussions and simulation results for NR V2X soft buffer combing test | Huawei, HiSilicon |
| 5.2.1.3.3 | PSFCH decoding capability test | |
| R4-2106038 | CR for 38.101-4: Introduction of PSFCH decoding capability test for NR V2X | Huawei, HiSilicon |
| R4-2106804 | Discussion on NR V2X PSFCH decoding capability test | Huawei, HiSilicon |
| R4-2106805 | CR for 38.101-4: Introduction of PSFCH decoding capability test for NR V2X. | Huawei, HiSilicon |
| 5.2.1.3.4 | PSCCH/PSSCH decoding capability | |
| R4-2104996 | Discussion on remaining isseu for PSCCH/PSSCH multiple link test | LG Electronics Inc. |
| R4-2106039 | CR for 38.101-4: Introduction of PSCCH/PSSCH capability test for NR V2X | Huawei, HiSilicon |
| R4-2106424 | Discussion on NR V2X Multiple Link PSCCH/PSSCH decoding capability requirements | Intel Corporation |
| R4-2106806 | Discussion on NR V2X PSCCH/PSSCH decoding capability test | Huawei, HiSilicon |
| R4-2106807 | CR for 38.101-4: Introduction of PSCCH/PSSCH capability test for NR V2X. | Huawei, HiSilicon |
| 5.3 | Integrated Access and Backhaul for NR | |
| R4-2106172 | WF on Rel-16 NR IAB demodulation requirements | Nokia |
| 5.3.1 | RF requirements Maintenance | |
| R4-2105974 | Email discussion summary for [98-bis-e][303] NR_IAB_RF_Maintenance | Moderator (CATT) |
| R4-2106137 | Email discussion summary for [98-bis-e][303] NR_IAB_RF_Maintenance | Moderator (CATT) |
| 5.3.1.1.1 | EVM procedure | |
| R4-2104781 | Discussion on open issues of IAB-MT EVM measurement | CATT |
| R4-2104782 | Draft CR for TS 38.174: IAB-MT EVM measurement | CATT |
| R4-2104783 | Draft CR for TR 38.809: IAB-MT EVM measurement | CATT |
| R4-2106040 | Draft CR for TS 38.174: IAB-MT EVM measurement | CATT |
| R4-2106041 | Draft CR for TR 38.809: IAB-MT EVM measurement | CATT |
| R4-2106667 | EVM measurement procedure considerations | Nokia, Nokia Shanghai Bell |
| R4-2107046 | IAB-MT conformance Test about EVM Equalizer | Keysight Technologies UK Ltd |
| R4-2107225 | IAB-MT EVM procedure | Ericsson |
| R4-2107226 | CR on Tx signal quality requirements | Ericsson |
| 5.3.1.1.2 | Others | |
| R4-2104784 | Draft CR for TS 38.174: Correction of IAB-DU class definition | CATT |
| R4-2106042 | Draft CR to TS 38.174 – corrections to general and transmitter part | Nokia, Nokia Shanghai Bell |
| R4-2106306 | Draft CR to TS 38.174 – corrections to general and transmitter part | Nokia, Nokia Shanghai Bell |
| R4-2107227 | CR on Tx Power related requirements | Ericsson |
| 5.3.1.2 | Receiver requirements | |
| R4-2106043 | Draft CR to TS 38.174 – corrections to receiver part | Nokia, Nokia Shanghai Bell |
| R4-2106307 | Draft CR to TS 38.174 – corrections to receiver part | Nokia, Nokia Shanghai Bell |
| R4-2107228 | CR on Rx Charateristic other related requirements | Ericsson |
| 5.3.2 | RF conformance testing | |
| R4-2105975 | Email discussion summary for [98-bis-e][304] NR_IAB_Conformance_Part1 | Moderator (Huawei) |
| 5.3.2.1 | General and work plan | |
| R4-2106044 | WF on Test models | Ericsson |
| R4-2106045 | WF on Test configurations | Nokia |
| R4-2106046 | WF on MU value tables | Huawei |
| R4-2106047 | WF on Test point reduction for shared IAB-DU and IAB-MT hardware | Ericsson |
| R4-2106050 | TP for Annex E for conducted IAB test specification | Ericsson |
| R4-2106051 | TP for Annex G and H for OTA IAB test specification | Ericsson |
| R4-2106058 | IAB conducted conformance specification skeleton | Huawei |
| R4-2106138 | Email discussion summary for [98-bis-e][304] NR_IAB_Conformance_Part1 | Moderator (Huawei) |
| R4-2106139 | Email discussion summary for [98-bis-e][305] NR_IAB_Conformance_Part2 | Moderator (Nokia) |
| R4-2106313 | Proposal on the skeleton of TS38.176-2 | Nokia, Nokia Shanghai Bell |
| R4-2106668 | IAB RF conformance testing coverage considerations | Nokia, Nokia Shanghai Bell |
| R4-2107233 | TP for Annex E for conducted IAB test specification | Ericsson |
| R4-2107234 | TP for Annex G and H for OTA IAB test specification | Ericsson |
| 5.3.2.2.1 | Test configurations | |
| R4-2104785 | TP for TS 38.176-1: Test configurations and applicability of requirements | CATT |
| R4-2104786 | TP for TS 38.176-2: Test configurations and applicability of requirements | CATT |
| R4-2106048 | TP for TS 38.176-1: Test configurations and applicability of requirements | CATT |
| R4-2106049 | TP for TS 38.176-2: Test configurations and applicability of requirements | CATT |
| R4-2106321 | Further considerations on IAB test configurations with TP to 38.176-1 and 38.176-2. | Nokia, Nokia Shanghai Bell |
| 5.3.2.2.2 | Test models | |
| R4-2106052 | IAB Common test issue on test model-Conducted | Ericsson |
| R4-2106053 | IAB Common test issue on test model-OTA | Ericsson |
| R4-2106322 | Further considerations on TDD pattern for IAB test models | Nokia, Nokia Shanghai Bell |
| R4-2107229 | IAB Common test issue on test model-Conducted | Ericsson |
| R4-2107230 | IAB Common test issue on test model-OTA | Ericsson |
| 5.3.2.2.3 | Others | |
| R4-2105036 | TP to TS38.176-1 on subclause 4.10 -5 | Samsung |
| R4-2105037 | TP to TS38.176-2 on subclause 4.10 -5 | Samsung |
| R4-2106054 | TP to TS38.176-1 on subclause 4.10 -5 | Samsung |
| R4-2106055 | TP to TS38.176-2 on subclause 4.10 -5 | Samsung |
| R4-2106056 | TP to TS 38.xxx-1: Section 4.2~4.5 | ZTE Corporation |
| R4-2106057 | TP to TS 38.xxx-2: Section 4.2~4.5 | ZTE Corporation |
| R4-2106059 | TP to TS 38.176-1 - Annex D | Huawei |
| R4-2106131 | TP to TS 38.176-1 -Clause 4.1 | Huawei |
| R4-2106595 | TP to TS 38.xxx-1: Section 4.2~4.5 | ZTE Corporation |
| R4-2106596 | TP to TS 38.xxx-2: Section 4.2~4.5 | ZTE Corporation |
| R4-2106669 | Remaining test setup considerations | Nokia, Nokia Shanghai Bell |
| R4-2107050 | IAB-MT conformance Test setup MU | Keysight Technologies UK Ltd |
| R4-2107096 | IAB - discussion on MU values | Huawei |
| R4-2107104 | TP to TS 38.176-1 - Annex D | Huawei |
| R4-2107237 | On IAB test case reduction for IAB Conducted conformance test | Ericsson |
| R4-2107238 | On IAB test case reduction for IAB OTA conformance test. | Ericsson |
| 5.3.2.3 | Conducted conformance testing | |
| R4-2105976 | Email discussion summary for [98-bis-e][305] NR_IAB_Conformance_Part2 | Moderator (Nokia) |
| R4-2107095 | IAB conducted conformance specification skeleton | Huawei |
| 5.3.2.3.1 | Transmitter characteristics | |
| R4-2104787 | TP for TS 38.176-1: Transmit ON/OFF power | CATT |
| R4-2104788 | TP for TS 38.176-1: Transmitted signal quality | CATT |
| R4-2105038 | View on Local Area IAB-MT power control testing | Samsung |
| R4-2106060 | TP to TS 38.176-1 - Tx dynamic range, clause 6.3 | Huawei |
| R4-2106062 | TP for TS 38.176-1: Transmit ON/OFF power | CATT |
| R4-2106063 | TP for TS 38.176-1: Transmitted signal quality | CATT |
| R4-2106064 | TP to TS 38.176-1: Output power and Unwanted emission | Nokia, Nokia Shanghai Bell |
| R4-2106065 | TP to TS 38.xxx-1: TX IMD requirements | ZTE Corporation |
| R4-2106315 | TP to TS 38.176-1: Output power and Unwanted emission | Nokia, Nokia Shanghai Bell |
| R4-2106597 | TP to TS 38.xxx-1: TX IMD requirements | ZTE Corporation |
| R4-2107098 | TP to TS 38.176-1 - Tx dynamic range, clause 6.3 | Huawei |
| R4-2107231 | On IAB-MT dynamic range and power control test for conduct test | Ericsson |
| 5.3.2.3.2 | Receiver characteristics | |
| R4-2106066 | P to TS 38.176-1 Annex A for IAB conducted test specification | Nokia, Nokia Shanghai Bell |
| R4-2106067 | TP to TS 38.xxx-1: RX IMD requirements | ZTE Corporation |
| R4-2106068 | TP to TS 38.xxx-1: RX ICS requirements | ZTE Corporation |
| R4-2106069 | TP toTS 38.176-1 - Sensitivity, clause 7.2 | Huawei |
| R4-2106070 | TP to TS 38.176-1 - Rx dynamic range, clause 7.3 | Huawei |
| R4-2106071 | TP for IBB, OBB and RX spurious of conducted receiver test | Ericsson |
| R4-2106316 | TP to TS 38.176-1 Annex A for IAB conducted test specification | Nokia, Nokia Shanghai Bell |
| R4-2106599 | TP to TS 38.xxx-1: RX IMD requirements | ZTE Corporation |
| R4-2106601 | TP to TS 38.xxx-1: RX ICS requirements | ZTE Corporation |
| R4-2107100 | TP toTS 38.176-1 - Sensitivity, clause 7.2 | Huawei |
| R4-2107102 | TP to TS 38.176-1 - Rx dynamic range, clause 7.3 | Huawei |
| R4-2107235 | TP for IBB, OBB and RX spurious of conducted receiver test | Ericsson |
| 5.3.2.3.3 | Other test issues | |
| R4-2104789 | TP for TS 38.176-1: Annex B and C | CATT |
| R4-2106072 | TP to TS 38.176-1 Clause 4.6 Declarations for IAB conducted test specification | Nokia, Nokia Shanghai Bell |
| R4-2106314 | TP to TS 38.176-1 Clause 4.6 Declarations for IAB conducted test specification | Nokia, Nokia Shanghai Bell |
| R4-2107097 | TP to TS 38.176-1 -Clause 4.1 | Huawei |
| 5.3.2.4.1 | Transmitter characteristics | |
| R4-2104790 | TP for TS 38.176-2: OTA transmit ON/OFF power | CATT |
| R4-2104791 | TP for TS 38.176-2: OTA transmitted signal quality | CATT |
| R4-2106061 | TP to TS 38.176-2 - OTA Tx dynamic range, clause 6.3 | Huawei |
| R4-2106073 | TP for TS 38.176-2: OTA transmit ON/OFF power | CATT |
| R4-2106074 | TP for TS 38.176-2: OTA transmitted signal quality | CATT |
| R4-2106075 | TP to TS 38.176-2: Output power and Unwanted emission | Nokia, Nokia Shanghai Bell |
| R4-2106076 | TP to TS 38.xxx-2: TX IMD requirements | ZTE Corporation |
| R4-2106319 | TP to TS 38.176-2: Output power and Unwanted emission | Nokia, Nokia Shanghai Bell |
| R4-2106598 | TP to TS 38.xxx-2: TX IMD requirements | ZTE Corporation |
| R4-2107099 | TP to TS 38.176-2 - OTA Tx dynamic range, clause 6.3 | Huawei |
| R4-2107232 | On IAB-MT dynamic range and power control test for OTA test | Ericsson |
| 5.3.2.4.2 | Receiver characteristics | |
| R4-2106077 | TP to TS 38.176-2 Annex A for IAB OTA test specification | Nokia, Nokia Shanghai Bell |
| R4-2106078 | TP to TS 38.xxx-2: RX IMD requirements | ZTE Corporation |
| R4-2106079 | P to TS 38.xxx-2: RX ICS requirements | ZTE Corporation |
| R4-2106080 | TP to TS 38.176-2 - OTA Sensitivity, clause 7.2, 7.3 | Huawei |
| R4-2106081 | TP to TS 38.176-2 - OTA Rx dynamic range, clause 7.3 | Huawei |
| R4-2106082 | TP on IBB, OBB and RX spurious for OTA receiver characteristic test | Ericsson |
| R4-2106317 | TP to TS 38.176-2 Annex A for IAB OTA test specification | Nokia, Nokia Shanghai Bell |
| R4-2106600 | TP to TS 38.xxx-2: RX IMD requirements | ZTE Corporation |
| R4-2106602 | TP to TS 38.xxx-2: RX ICS requirements | ZTE Corporation |
| R4-2107101 | TP to TS 38.176-2 - OTA Sensitivity, clause 7.2, 7.3 | Huawei |
| R4-2107103 | TP to TS 38.176-2 - OTA Rx dynamic range, clause 7.3 | Huawei |
| R4-2107236 | TP on IBB, OBB and RX spurious for OTA receiver characteristic test | Ericsson |
| 5.3.2.4.3 | Other test issues | |
| R4-2104792 | TP for TS 38.176-2: Annex B and C | CATT |
| R4-2106083 | TP to TS 38.146-2 Clause 4.6 Declarations for IAB radiated test specification | Nokia, Nokia Shanghai Bell |
| R4-2106084 | TP to TS 38.176-2 - Annex D&E | Huawei |
| R4-2106318 | TP to TS 38.146-2 Clause 4.6 Declarations for IAB radiated test specification | Nokia, Nokia Shanghai Bell |
| R4-2107105 | TP to TS 38.176-2 - Annex D&E | Huawei |
| 5.3.3 | RRM perf. requirements | |
| R4-2105805 | Email discussion summary: [98-bis-e][203] NR_IAB_RRM | Moderator (ZTE) |
| 5.3.3.1 | General | |
| R4-2104482 | On IAB test cases | ZTE Corporation |
| R4-2105673 | Email discussion summary for [98-bis-e][203] NR IAB RRM | Moderator (ZTE Corporation) |
| R4-2105729 | Draft CR on maintenance for IAB-MT RRM test cases | Huawei, HiSilicon |
| R4-2105730 | Big CR: IAB-MT RRM test cases in 38.174 | Ericsson |
| R4-2105847 | WF on test cases for IAB-MTs | ZTE |
| R4-2106950 | Discussion on RRM performance requirements for IAB | Huawei, HiSilicon |
| R4-2106951 | Draft CR on maintenance for IAB-MT RRM test cases | Huawei, HiSilicon |
| R4-2107133 | Big CR: IAB-MT RRM test cases in 38.174 | Ericsson |
| R4-2107134 | Analysis of side conditions for IAB-MT RRM test cases | Ericsson |
| R4-2107135 | Side conditions for IAB-MT RRM test cases in TS 38.174 | Ericsson |
| 5.3.3.2.2 | RRC Connection Release with Redirection | |
| R4-2106952 | Draft CR on test cases for RRC release with redirection for IAB-MT | Huawei, HiSilicon |
| 5.3.3.2.3 | IAB-MT transmit timing | |
| R4-2104930 | [draft CR] Test cases for timing for IAB-MT | ZTE Corporation |
| R4-2105733 | [draft CR] Test cases for timing for IAB-MT | ZTE |
| 5.3.3.2.4 | RLM | |
| R4-2107136 | Analysis of CSI-RS based RLM tests for LA IAB-MT | Ericsson |
| R4-2107137 | CSI-RS based RLM tests for LA IAB-MT in TS 38.174 | Ericsson |
| 5.3.3.2.5 | Beam Failure Detection and Link Recovery | |
| R4-2104928 | [draft CR] Test cases for Beam Failure Detection and Link Recovery with CSI-RS in FR1 | ZTE Corporation |
| R4-2104929 | [draft CR] Test cases for Beam Failure Detection and Link Recovery with SSB in FR1 | ZTE Corporation |
| R4-2105731 | [draft CR] Test cases for Beam Failure Detection and Link Recovery with CSI-RS in FR1 | ZTE |
| R4-2105732 | [draft CR] Test cases for Beam Failure Detection and Link Recovery with SSB in FR1 | ZTE |
| R4-2105734 | Draft CR to introduce test cases for BFD and LR based on SSB in FR2 for IAB-MT | Huawei, HiSilicon |
| R4-2105735 | draftCR on test cases for CSI-RS based BFD and LR for IAB-MTs | Nokia, Nokia Shanghai Bell |
| R4-2106953 | Draft CR to introduce test cases for BFD and LR based on SSB in FR2 for IAB-MT | Huawei, HiSilicon |
| R4-2107220 | draftCR on test cases for CSI-RS based BFD and LR for IAB-MTs | Nokia, Nokia Shanghai Bell |
| 5.3.4 | EMC performance requirements | |
| R4-2104960 | Further discussion on IAB RI testing with spatial exclusions | ZTE Corporation |
| R4-2105973 | Email discussion summary for [98-bis-e] [302] NR_EMC | Moderator (ZTE Corporation) |
| R4-2106085 | WF on IAB EMC spatial exclusion | Ericsson |
| R4-2106086 | Draft CR to TS 38.175 on IAB EMC test configurations and performance requirements | Ericsson, ZTE |
| R4-2106140 | Email discussion summary for [98-bis-e][302] NR_EMC | Moderator (ZTE) |
| R4-2106510 | Discussion on Performance criteria for transient phenomena for IAB | Ericsson |
| R4-2106511 | Draft CR to TS 38.175 on IAB EMC test configurations and performance requirements | Ericsson, ZTE |
| R4-2106512 | Discussion on Spatial Exclusion for IAB EMC RI test | Ericsson |
| R4-2106513 | Draft CR to TS 38.175 on Spatial Exclusion for IAB EMC Radiated Immunity test | Ericsson |
| 5.3.5 | Demodulation and CSI requirements | |
| R4-2105990 | Email discussion summary for [98-bis-e][319] NR_IAB_Demod | Moderator (Nokia, Nokia Shanghai Bell) |
| 5.3.5.1 | General | |
| R4-2104660 | pCR to 38.176-1: Introduction of annexes on test tolerance, test setup and propagation conditions for performance requirements | Ericsson |
| R4-2104661 | Draft CR to 38.174: FRCs and PRACH preambles | Ericsson |
| R4-2106088 | WF on Rel-16 NR IAB demodulation requirements | Nokia |
| R4-2106089 | WF on Rel-16 NR IAB specification editorial issues | Ericsson |
| R4-2106141 | Email discussion summary for [98-bis-e][319] NR_IAB_Demod | Moderator (Nokia) |
| R4-2106438 | draftCR to 38.174: IAB-MT and IAB-DU performance requirements | Intel Corporation |
| R4-2106439 | TP to TS 38.176-1: FRC and PRACH test preambles | Intel Corporation |
| R4-2106440 | TP to TS 38.176-2: Demodulation manufacturer declarations | Intel Corporation |
| R4-2106441 | Big TP to TS 38.176-1: IAB demodulation performance requirements | Intel Corporation |
| R4-2106778 | draftTP to TS 38.176-2 IAB-DU performance requirements and parts of DU and MT appendix | Nokia, Nokia Shanghai Bell |
| R4-2106817 | Big CR on IAB-MT demodulation in TS 38.174 | Huawei, HiSilicon |
| R4-2106819 | pCR on IAB conducted conformance testing (Manufacturer declarations) to TS 38.176-1 | Huawei, HiSilicon |
| R4-2106822 | pCR on IAB radiated conformance testing (FRCs and PRACH test preambles) to TS 38.176-2 | Huawei, HiSilicon |
| R4-2107094 | bigTP draft to TS 38.176-2 Demodulation performance | Nokia, Nokia Shanghai Bell |
| 5.3.5.2 | IAB-DU performance requirements | |
| R4-2104659 | Draft CR to 38.174: Introduction of IAB-DU performance requirements | Ericsson |
| R4-2104664 | IAB-DU remaining issues | Ericsson |
| R4-2106433 | Views on IAB-DU demodulation performance requirements | Intel Corporation |
| R4-2106777 | On IAB-DU demodulation requirements | Nokia, Nokia Shanghai Bell |
| R4-2106812 | Discussion on NR IAB-DU demodulation performance requirements | Huawei, HiSilicon |
| R4-2107251 | draftTP to TS 38.176-1 IAB-DU performance requirements | Nokia, Nokia Shanghai Bell |
| 5.3.5.3 | IAB-MT performance requirements | |
| R4-2104662 | pCR to 38.176-2: Introduction of CSI-RS performance tests and requirements | Ericsson |
| R4-2104663 | pCR to 38.176-1: IAB-MT performance tests | Ericsson |
| R4-2104665 | IAB-MT remaining issues | Ericsson |
| R4-2104666 | IAB-MT simulation results | Ericsson |
| R4-2106434 | Views on IAB-MT demodulation performance requirements | Intel Corporation |
| R4-2106571 | On IAB-MT demodulation requirements | Nokia, Nokia Shanghai Bell |
| R4-2106779 | draftCR to TS 38.174 CSI reporting radiated performance requirements | Nokia, Nokia Shanghai Bell |
| R4-2106813 | Discussion on NR IAB-MT demodulation performance requirements | Huawei, HiSilicon |
| R4-2106814 | Simulation results for NR IAB-MT demodulation performance requirements | Huawei, HiSilicon |
| R4-2106815 | Updated simulation assumptions for NR IAB-MT demodulation requirements | Huawei, HiSilicon |
| R4-2106816 | Summary of simulation results for NR IAB-MT demodulation requirements | Huawei, HiSilicon |
| R4-2106818 | Draft CR on IAB-MT conducted performance requirements (General and Demodulation) in TS 38.174 | Huawei, HiSilicon |
| R4-2106820 | pCR on IAB-MT conducted conformance testing (CSI reporting and Interworking) to TS 38.176-1 | Huawei, HiSilicon |
| R4-2106821 | pCR on IAB-MT radiated conformance testing (General and Demodulation) to TS 38.176-2 | Huawei, HiSilicon |
| 5.4 | Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements | |
| R4-2105806 | Email discussion summary: [98-bis-e][204] LTE_NR_DC_CA_RRM_1_NWM | Moderator (Nokia) |
| R4-2105807 | Email discussion summary: [98-bis-e][205] LTE_NR_DC_CA_RRM_2 | Moderator (Ericsson) |
| 5.4.1 | RRM core requirements maintenance (38.133/36.133) | |
| R4-2105674 | Email discussion summary: [98-bis-e][204] LTE_NR_DC_CA_RRM_1_NWM | Moderator (Nokia) |
| 5.4.1.1 | Early Measurement reporting | |
| R4-2106990 | CR on LTE-NR EMR requirements 36133 | Huawei, HiSilicon |
| R4-2106991 | CR on EMR requirements correction 38133 | Huawei, HiSilicon |
| 5.4.1.2 | Efficient and low latency serving cell configuration, activation and setup | |
| R4-2104860 | Core requirement maintenance on direct SCell activation | Apple |
| R4-2104861 | CR for core requirement maintenance on direct SCell activation | Apple |
| R4-2105675 | Email discussion summary for [98-bis-e][205] LTE_NR_DC_CA_RRM_2 | Moderator (Ericsson) |
| R4-2105739 | CR for core requirement maintenance on direct SCell activation | Apple |
| R4-2105740 | Draft CR Correction of activation delay for Direct activated Scell | Nokia, Nokia Shanghai Bell |
| R4-2105741 | CR on direct SCell activation | Huawei, HiSilicon |
| R4-2106387 | Discussion on Tactivation_time for Direct SCell activation | Nokia, Nokia Shanghai Bell |
| R4-2106388 | Draft CR Correction of activation delay for Direct activated Scell | Nokia, Nokia Shanghai Bell |
| R4-2106885 | Core maintenance for Direct SCell activation | Ericsson |
| R4-2106993 | CR on direct SCell activation | Huawei, HiSilicon |
| R4-2106994 | CR on SCell dormancy requirements | Huawei, HiSilicon |
| 5.4.2.1.1 | General | |
| R4-2105736 | WF on Test cases for MR-DC Idle mode CA measurements | Nokia, Nokia Shanghai Bell |
| R4-2105737 | Draft CR for Idle Mode measurements of inter-frequency RAT CA candidate cells for early reporting (TC#3) | Nokia, Nokia Shanghai Bell |
| R4-2105841 | WF on Test cases for MR-DC Idle mode CA measurements | Nokia |
| R4-2106389 | Measurement Performance Requirements test for MR-DC | Nokia, Nokia Shanghai Bell |
| R4-2106390 | Draft CR for Idle Mode measurements of inter-frequency RAT CA candidate cells for early reporting (TC#3) | Nokia, Nokia Shanghai Bell |
| R4-2106391 | Draft Big CR: Introduction of Rel-16 MR-DC EMR RRM performance requirements (TS 38.133) | Nokia, Nokia Shanghai Bell |
| 5.4.2.1.3 | Test cases | |
| R4-2104859 | Testing of measurement performance for RSRP/RSRQ in EMR | Apple |
| R4-2106992 | draftCR to update EMR TC4 | Huawei, HiSilicon |
| 5.4.2.2.1 | General | |
| R4-2105738 | WF on maintenance of Direct SCell activation and SCell dormancy | Ericsson |
| R4-2105742 | Draft Big CR 38.133: Introduction of Rel-16 MR-DC Direct SCell activation and SCell dormancy RRM performance requirements | Ericsson |
| R4-2106884 | Draft Big CR 38.133: Introduction of Rel-16 MR-DC Direct SCell activation and SCell dormancy RRM performance requirements | Ericsson |
| 5.4.2.2.3 | Test case for SCell Dormancy | |
| R4-2106995 | Discussion on remaining issues for SCell dormancy tests | Huawei, HiSilicon |
| R4-2106996 | draftCR on SCell dormancy TC | Huawei, HiSilicon |
| 5.5.1 | RRM core requirements maintenance (38.133) | |
| R4-2105676 | Email discussion summary for [98-bis-e][206] NR_pos_1 | Moderator (Huawei) |
| R4-2105743 | WF on UE PRS measurement requirements | Huawei, HiSilicon |
| R4-2105808 | Email discussion summary: [98-bis-e][206] NR_pos_1 | Moderator (Huawei) |
| R4-2105851 | WF on UE PRS measurement requirements | Huawei, HiSilicon |
| 5.5.1.1 | PRS-RSTD measurement requirements | |
| R4-2104427 | [draft CR] Core maintenance for NR Positioning | ZTE Corporation |
| R4-2104741 | Discussion on PRS RSTD measurement requirements | CATT |
| R4-2104743 | CR on PRS RSTD measurement requirements | CATT |
| R4-2105744 | CR on PRS RSTD measurement requirements | CATT |
| R4-2106334 | On PRS-RSTD measurement requirements | Qualcomm Incorporated |
| R4-2106452 | Further discussion on NR PRS RSTD measurement report requirements | Intel Corporation |
| R4-2106515 | Discussion on RSTD measurement requirements | OPPO |
| R4-2106624 | Further discussion on PRS RSTD measurement requirements | vivo |
| R4-2106628 | CR to 38.133 correction to PRS RSTD measurement requirements | vivo |
| R4-2106997 | Discussion on remaining issues for RSTD measurement requirements | Huawei, HiSilicon |
| R4-2106998 | CR to update RSTD measurement requirements | Huawei, HiSilicon |
| R4-2107159 | On RSTD measurement requirements | Ericsson |
| R4-2107160 | RSTD measurement requirements | Ericsson |
| R4-2107181 | On PRS-RSTD measurement period definition | Nokia, Nokia Shanghai Bell |
| 5.5.1.2 | PRS-RSRP measurement requirements | |
| R4-2105745 | PRS-RSRP measurement requirements | Ericsson |
| R4-2106335 | On PRS-RSRP measurement requirements | Qualcomm Incorporated |
| R4-2106625 | Discussion on PRS-RSRP measurement requirements | vivo |
| R4-2106629 | CR to 38.133 correction on PRS-RSRP measurement requirements | vivo |
| R4-2106999 | Discussion on remaining issues for PRS-RSRP measurement requirements | Huawei, HiSilicon |
| R4-2107000 | CR to update PRS-RSRP measurement requirements | Huawei, HiSilicon |
| R4-2107161 | On PRS-RSRP measurement requirements | Ericsson |
| R4-2107162 | PRS-RSRP measurement requirements | Ericsson |
| R4-2107182 | On PRS-RSRP measurement period definition | Nokia, Nokia Shanghai Bell |
| 5.5.1.3 | UE Rx-Tx time difference measurement requirements | |
| R4-2104742 | Discussion on UE Rx-Tx time difference measurement requirements | CATT |
| R4-2104744 | CR on UE Rx-Tx time difference measurement requirements | CATT |
| R4-2105746 | CR to TS 38.133 on UE Rx-Tx time difference measurements | OPPO |
| R4-2106336 | On UE Rx-Tx measurement requirements | Qualcomm Incorporated |
| R4-2106453 | Discussion on UE RX-TX time difference measurement requirements | Intel Corporation |
| R4-2106516 | Discussion on maintenance for UE Rx-Tx time difference measurements | OPPO |
| R4-2106517 | CR to TS 38.133 on UE Rx-Tx time difference measurements | OPPO |
| R4-2106626 | Further discussion on UE RX-TX timing difference measurement requirements | vivo |
| R4-2106630 | CR to 38.133 correction on UE Rx-Tx timing difference measurement requirements | vivo |
| R4-2107001 | Discussion on remaining issues for UE Rx-Rx time difference measurement requirements | Huawei, HiSilicon |
| R4-2107002 | CR to update UE Rx-Tx time difference measurement requirements | Huawei, HiSilicon |
| R4-2107163 | On UE Rx-Tx measurement requirements | Ericsson |
| R4-2107164 | UE Rx-Tx measurement requirements | Ericsson |
| R4-2107183 | On UE RX-TX measurement period definition | Nokia, Nokia Shanghai Bell |
| 5.5.1.4 | Other requirements | |
| R4-2105747 | CR to 38.133 correction on CCSF for NR measurements for positioning | vivo |
| R4-2105748 | CR on CSSF, measurement capability and MG for PRS measurement 38.133 | Huawei, HiSilicon |
| R4-2105749 | CR to remove measurement gap pattern #25 for LTE measurement in 36.133 | Huawei, HiSilicon |
| R4-2106337 | On general PRS measurement requirements | Qualcomm Incorporated |
| R4-2106518 | Others requirements: maintenance for general PRS measurements | OPPO |
| R4-2106627 | Further discussion on general requirements for NR positioning | vivo |
| R4-2106631 | CR to 38.133 correction on CCSF for NR measurements for positioning | vivo |
| R4-2107003 | Discussion on CSSF, measurement capability and MG for PRS measurement | Huawei, HiSilicon |
| R4-2107004 | CR on CSSF, measurement capability and MG for PRS measurement 38.133 | Huawei, HiSilicon |
| R4-2107005 | CR to remove measurement gap pattern #25 for LTE measurement in 36.133 | Huawei, HiSilicon |
| R4-2107184 | Discussion on other NR positioning requirements | Nokia, Nokia Shanghai Bell |
| 5.5.2 | RRM perf. requirements (38.133) | |
| R4-2105750 | WF on NR Positioning UE Performance Requirements | Intel Corporation |
| R4-2105809 | Email discussion summary: [98-bis-e][207] NR_pos_2 | Moderator (Intel Corporation) |
| 5.5.2.1 | General | |
| R4-2105751 | Draft Big CR: Introduction of Rel-16 NR Positioning RRM performance requirements and test cases | Ericsson, Intel |
| R4-2107158 | Draft Big CR: Introduction of Rel-16 NR Positioning RRM performance requirements and test cases | Ericsson, Intel |
| R4-2107216 | Summary of all link level accuracy simulation results for RSTD, PRS-RSRP, and UE Rx-Tx | Ericsson |
| 5.5.2.2 | UE requirements and test cases | |
| R4-2105677 | Email discussion summary for [98-bis-e][207] NR_pos_RRM_Part_2 | Moderator (Intel Corporation) |
| R4-2105829 | draftCR to introduce accuracy requirements for RSTD measurement | Huawei, HiSilicon |
| R4-2105843 | draftCR to introduce accuracy requirements for RSTD measurement | Huawei, HiSilicon |
| 5.5.2.2.1 | General | |
| R4-2105754 | Summary of link level simulation result of RSTD, PRS RSRP and UE Rx-Tx time difference | Intel Corporation |
| R4-2105848 | Summary of link level simulation result of RSTD, PRS RSRP and UE Rx-Tx time difference | Intel Corporation |
| R4-2105852 | Summary of link level simulation result of RSTD, PRS RSRP and UE Rx-Tx time difference | Intel Corporation |
| R4-2105857 | Summary of link level simulation result of RSTD, PRS RSRP and UE Rx-Tx time difference | Intel Corporation |
| R4-2106457 | Summary of link level simulation result of RSTD, PRS RSRP and UE Rx-Tx time difference | Intel Corporation |
| R4-2106519 | Simulation results of link level simulation result of RSTD and PRS RSRP | OPPO |
| R4-2107169 | On positioning test cases | Ericsson |
| 5.5.2.2.2 | Measurement accuracy requirements | |
| R4-2106343 | NR Pos performance simulation results | Qualcomm Incorporated |
| 5.5.2.2.2.1 | PRS RSTD | |
| R4-2104745 | Discussion on PRS RSTD accuracy requirements | CATT |
| R4-2106338 | On PRS-RSTD measurement accuracy requirements | Qualcomm Incorporated |
| R4-2106454 | Further Discussion on NR PRS RSTD Measurement Accuracy Requirements | Intel Corporation |
| R4-2106520 | Discussion on PRS RSTD accuracy requirements | OPPO |
| R4-2106632 | Further discussion on PRS RSTD accuracy requirements | vivo |
| R4-2106635 | Link level simulation results for PRS RSTD | vivo |
| R4-2107006 | Discussion on accuracy requirements for RSTD measurement | Huawei, HiSilicon |
| R4-2107007 | draftCR to introduce accuracy requirements for RSTD measurement | Huawei, HiSilicon |
| R4-2107165 | On RSTD measurement accuracy requirements | Ericsson |
| 5.5.2.2.2.2 | PRS RSRP | |
| R4-2104746 | Discussion on PRS RSRP accuracy requirements | CATT |
| R4-2104747 | CR on PRS-RSRP accuracy requirements | CATT |
| R4-2105753 | CR on PRS-RSRP accuracy requirements | CATT |
| R4-2105845 | CR on PRS-RSRP accuracy requirements | CATT |
| R4-2106339 | On PRS-RSRP measurement accuracy requirements | Qualcomm Incorporated |
| R4-2106456 | Discussion on PRS RSRP accuracy requirements for NR Positioning | Intel Corporation |
| R4-2106521 | Discussion on PRS RSRP accuracy requirements | OPPO |
| R4-2106633 | Discussion on PRS-RSRP accuracy requirements | vivo |
| R4-2106636 | Link level simulation results for PRS-RSRP | vivo |
| R4-2107008 | Discussion on accuracy requirements for PRS-RSRP measurement | Huawei, HiSilicon |
| R4-2107166 | On PRS-RSRP measurement accuracy requirements | Ericsson |
| 5.5.2.2.2.3 | UE Rx-Tx time difference | |
| R4-2105752 | UE Rx-Tx measurement accuracy requirements | Ericsson |
| R4-2105844 | UE Rx-Tx measurement accuracy requirements | Ericsson |
| R4-2106340 | On UE Rx-Tx measurement accuracy requirements | Qualcomm Incorporated |
| R4-2106455 | Discussion on UE RX-TX time difference measurement accuracy requirements | Intel Corporation |
| R4-2106522 | Discussion on accuracy requirements for UE Rx-Tx time difference | OPPO |
| R4-2106634 | Discussion on UE Rx-Tx timing difference accuracy requirements | vivo |
| R4-2106637 | Link level simulation results for UE Rx-Tx timing difference | vivo |
| R4-2107009 | Discussion on accuracy requirements for UE Rx-Tx time difference measurement | Huawei, HiSilicon |
| R4-2107167 | On UE Rx-Tx measurement accuracy requirements | Ericsson |
| R4-2107168 | UE Rx-Tx measurement accuracy requirements | Ericsson |
| 5.5.2.2.3.1 | General | |
| R4-2105837 | [draftCR] PRS configurations for NR Pos RRM tests | Intel Corporation |
| R4-2106341 | Design of test cases for NR positioning | Qualcomm Incorporated |
| R4-2106449 | Discussion on NR Positioning test cases configuration | Intel Corporation |
| R4-2106450 | [draftCR] PRS configurations for NR Pos RRM tests | Intel Corporation |
| R4-2106523 | Discussion on remaining issues of test cases for NR positioning | OPPO |
| R4-2107010 | Discussion on RRM test case for UE positioning requirements | Huawei, HiSilicon |
| R4-2107048 | Test case design principles for NR Positioning | ZTE Corporation |
| 5.5.2.2.3.2 | Measurement requirements | |
| R4-2104748 | CR on test case for PRS-RSRP measurement requirements for FR2 in SA | CATT |
| R4-2106451 | [draftCR] Test case of RSTD measurement requirements reporting in SA | Intel Corporation |
| R4-2107011 | draftCR to introduce TC for PRS-RSRP measurement requirements for FR1 in SA | Huawei, HiSilicon |
| R4-2107170 | TC5 and TC6: UE Rx-Tx time difference measurement requirements for FR1 and FR2 in SA | Ericsson |
| 5.5.2.2.3.3 | Accuracy requirements | |
| R4-2106921 | [draft CR] Test cases for PRS-RSRP measurement accuracy | ZTE Corporation |
| R4-2107012 | draftCR to introduce TC for RSTD measurement accuracy for FR1 and FR2 in SA | Huawei, HiSilicon |
| R4-2107171 | TC11 and TC12: UE Rx-Tx time difference measurement accuracy for FR1 and FR2 in SA | Ericsson |
| 5.5.2.3 | gNB requirements | |
| R4-2105678 | Email discussion summary for [98-bis-e][208] NR_pos_3 | Moderator (Ericsson) |
| R4-2105755 | WF on gNB positioning measurement requirements | Ericsson |
| R4-2105810 | Email discussion summary: [98-bis-e][208] NR_pos_3 | Moderator (Ericsson) |
| 5.5.2.3.1 | General | |
| R4-2105758 | Updated link level simulation assumption for gNB positioning measurement performance | Huawei, HiSilicon |
| R4-2106399 | Summary of link level simulation results of SRS RSRP and gNB TOA | Ericsson |
| R4-2106400 | gNB positioning link level simulation results | Ericsson |
| R4-2106922 | Beam configuration for gNB measurement accuracy | ZTE Corporation |
| R4-2107013 | Discussion on general issues for gNB positioning measurement requirements | Huawei, HiSilicon |
| R4-2107014 | Updated link level simulation assumption for gNB positioning measurement performance | Huawei, HiSilicon |
| R4-2107177 | General aspects for gNB measurement accuracy requirements | Nokia, Nokia Shanghai Bell |
| 5.5.2.3.2 | SRS-RSRP requirements | |
| R4-2105756 | gNB SRS-RSRP measurement | Ericsson |
| R4-2106401 | gNB SRS-RSRP requirements | Ericsson |
| R4-2106403 | gNB SRS-RSRP measurement | Ericsson |
| R4-2106948 | Link level simulation results for SRS-RSRP | Huawei, HiSilicon |
| R4-2107017 | Discussion on SRS-RSRP requirements | Huawei, HiSilicon |
| R4-2107018 | draftCR to introduce SRS-RSRP requirements | Huawei, HiSilicon |
| R4-2107178 | Link simulation results for SRS-RSRP accuracy | Nokia, Nokia Shanghai Bell |
| 5.5.2.3.3 | gNB Rx-Tx time difference requirements | |
| R4-2104749 | Discussion on gNB Rx-Tx time difference measurement requirements | CATT |
| R4-2105757 | draftCR to introduce gNB Rx-Tx time difference requirements | Huawei, HiSilicon |
| R4-2106342 | On gNB Rx-Tx measurement accuracy requirements | Qualcomm Incorporated |
| R4-2106404 | gNB Rx-Tx time difference requirements | Ericsson |
| R4-2106405 | gNB Rx-Tx measurement | Ericsson |
| R4-2106949 | Link level simulation results for gNB TOA measurement | Huawei, HiSilicon |
| R4-2107015 | Discussion on gNB Rx-Tx time difference requirements | Huawei, HiSilicon |
| R4-2107016 | draftCR to introduce gNB Rx-Tx time difference requirements | Huawei, HiSilicon |
| R4-2107179 | Link simulation results for gNB Rx-Tx time difference accuracy | Nokia, Nokia Shanghai Bell |
| 5.5.2.3.4 | UL RTOA requirements | |
| R4-2106406 | UL RTOA requirements | Ericsson |
| R4-2106407 | UL RTOA requirements | Ericsson |
| R4-2107019 | Discussion on UL-RTOA requirements | Huawei, HiSilicon |
| R4-2107020 | draftCR to introduce UL-RTOA requirements | Huawei, HiSilicon |
| R4-2107180 | On UL-RTOA requirements for NR positioning | Nokia, Nokia Shanghai Bell |
| 5.6 | NR RRM requirement enhancement | |
| R4-2105681 | [98-bis-e][211] NR_RRM_Enh_3_NWM - Version 0.0.4 | Moderator (Apple) |
| R4-2105759 | WF on R16 RRM enhancement part 1 – BWP switching, UL spatial relation switch | Intel Corporation |
| R4-2105761 | WF on R16 RRM enhancement part 2 – SRS Carrier switching, CGI reading, Mandatory MG patterns | ZTE |
| R4-2105811 | Email discussion summary: [98-bis-e][209] NR_RRM_Enh_1 | Moderator (Intel Corporation) |
| R4-2105812 | Email discussion summary: [98-bis-e][210] NR_RRM_Enh_2 | Moderator (ZTE) |
| R4-2105813 | Email discussion summary: [98-bis-e][211] NR_RRM_Enh_3 | Moderator (Apple) |
| 5.6.1 | RRM core requirements maintenance (38.133) | |
| R4-2104481 | Interruption requirements for SRS carrier based switching between different FR | ZTE Corporation |
| R4-2104630 | Regarding RRC based BWP switch for Scell | vivo |
| R4-2104842 | On Core Requirements Maintenance for RRM Enhancements | Apple |
| R4-2105003 | Draft CR on UL spatial relation info switch for PUCCH | Apple |
| R4-2105137 | draftCR on TS38.133 for inter-freq meas without gap | Ericsson, Mediatek |
| R4-2105679 | Email discussion summary for [98-bis-e][209]NR_RRM_Enh_1 | Moderator (Intel Corporation) |
| R4-2105680 | Email discussion summary for [98-bis-e][210] NR_RRM_Enh_2 | Moderator (ZTE Corporation) |
| R4-2105762 | Correction on SRS carrier switching | Huawei, HiSilicon |
| R4-2105766 | draftCR on TS38.133 for inter-freq meas without gap | Ericsson, MediaTek |
| R4-2105767 | CR on the measurement requirements of needforgap | Huawei, HiSilicon |
| R4-2105768 | CR on remaining issues in multiple SCell activation | Huawei, HiSilicon |
| R4-2105835 | draftCR on RRC-based BWP switch on multiple CCs | Nokia, Nokia Shanghai Bell |
| R4-2105836 | DraftCR on maintenance of BWP Switch on multiple CCs TS38.133 | Huawei, HiSilicon |
| R4-2105840 | Draft CR on UL spatial relation info switch for PUCCH | Apple |
| R4-2106458 | Discussion on remaining issues for RRM enhancement in Rel-16 | Intel Corporation |
| R4-2106460 | CR on RRC based BWP switching on multiple CCs | Intel Corporation |
| R4-2106524 | Discussion on remaining issues for BWP switching on multiple CCs | OPPO |
| R4-2106611 | Draft CR to 38.133 correction on SRS carrier based switching core requirements | vivo, Qualcomm, Huawei, HiSilicon, MediaTek Inc., Apple, Nokia |
| R4-2106612 | Further discussion on SRS carrier switching between FR1 and FR2 | vivo |
| R4-2106930 | Correction on SRS carrier switching | Huawei, HiSilicon |
| R4-2106932 | Discussion on the needforgap measurement | Huawei, HiSilicon |
| R4-2106933 | CR on the measurement requirements of needforgap | Huawei, HiSilicon |
| R4-2106934 | Discussion on uplink spatial relation switch delay for PL-RS | Huawei, HiSilicon |
| R4-2106935 | Update on uplink spatial relation switch delay | Huawei, HiSilicon |
| R4-2106954 | Discussion on RRM requirements for RRC based BWP switch on multiple CCs | Huawei, HiSilicon |
| R4-2106955 | DraftCR on maintenance of BWP Switch on multiple CCs TS38.133 | Huawei, HiSilicon |
| R4-2106956 | DraftCR on maintenance of BWP Switch on multiple CCs TS36.133 | Huawei, HiSilicon |
| R4-2107021 | Discussion on remaining issues in multiple SCell activation | Huawei, HiSilicon |
| R4-2107022 | CR on remaining issues in multiple SCell activation | Huawei, HiSilicon |
| R4-2107154 | Analysis of RRC based BWP switch on multiple CCs | Ericsson |
| R4-2107155 | Correction to RRC based BWP change delay requirements | Ericsson |
| R4-2107221 | discussion on RRC-based BWP switch on multiple CCs | Nokia, Nokia Shanghai Bell |
| R4-2107222 | draftCR on RRC-based BWP switch on multiple CCs | Nokia, Nokia Shanghai Bell |
| R4-2107287 | Maintenance on FR1 SCell Activation | Qualcomm Incorporated |
| 5.6.2.2.1 | SRS carrier switching requirements | |
| R4-2104899 | CR: SRS carrier switching TCs | Qualcomm, Inc. |
| R4-2105763 | Draft CR to 38.133 correction on SRS carrier based switching test cases | vivo |
| R4-2106613 | Draft CR to 38.133 correction on SRS carrier based switching test cases | vivo |
| 5.6.2.2.2 | Multiple Scell activation/deactivation | |
| R4-2107288 | Test cases with OTA testability | Qualcomm Incorporated |
| 5.6.2.2.3 | CGI reading requirements with autonomous gap | |
| R4-2104568 | DraftCR on SA CGI identification of E-UTRA neighbor cell Test Case | MediaTek inc. |
| R4-2104900 | CR: CGI reading TCs | Qualcomm, Inc. |
| R4-2105764 | CR: CGI reading TCs | Qualcomm |
| 5.6.2.2.4 | BWP switching on multiple CCs | |
| R4-2106957 | Discussion on performance requirements on RRC based BWP switch on multiple CCs | Huawei, HiSilicon |
| R4-2106958 | Draft CR on RRC based BWP switch on multiple CCs | Huawei, HiSilicon |
| R4-2107223 | discussion on test cases for RRC-based BWP switch on multiple CCs | Nokia, Nokia Shanghai Bell |
| 5.6.2.2.6 | Mandatory MG patterns | |
| R4-2104480 | On test cases for mandatory gap patterns | ZTE Corporation |
| R4-2104862 | Test applicability for mandatory gap patterns | Apple |
| R4-2104863 | CR for test applicability for mandatory gap patterns | Apple |
| R4-2104947 | Discussion on test cases for mandatory MG patterns | CMCC |
| R4-2105765 | CR for test applicability for mandatory gap patterns | Apple |
| R4-2106886 | On test case applicability for mandatory measurement gaps in R15/R16 | Ericsson |
| R4-2106931 | Discussion on mandatory gap pattern test | Huawei, HiSilicon |
| 5.6.2.2.8 | Spatial relation switch for uplink | |
| R4-2104901 | CR: UL spatial relation TCs | Qualcomm, Inc. |
| R4-2105760 | CR: UL spatial relation TCs | Qualcomm, Inc. |
| 5.7.1 | RRM core requirements maintenance (38.133) | |
| R4-2104692 | Discussion on the remaining issues for CSI-RS L3 measurement | Xiaomi |
| R4-2104733 | Discussion on core part maintenance open issues | CATT |
| R4-2104734 | draft CR on CSI-RS based L3 measurement | CATT |
| R4-2104836 | On remaining issues of RRM core requirements for CSI-RS based L3 measurement | Apple |
| R4-2105682 | Email disc+B1284:R1284ussion summary: [98-bis-e][212] NR_CSIRS_L3meas_1 | Moderator (CATT) |
| R4-2105770 | WF on core part maintenance of CSI-RS based L3 measurement requirements | Apple |
| R4-2105772 | draft CR on CSI-RS based L3 measurement | CATT |
| R4-2105773 | Draft CR to 38.133 Correction on core requirements for CSI-RS based measurement | vivo |
| R4-2105774 | CR on CSI-RS measurement window and intra-frequency measurements | Huawei, HiSilicon |
| R4-2105814 | Email disc+B1284:R1284ussion summary: [98-bis-e][212] NR_CSIRS_L3meas_1 | Moderator (CATT) |
| R4-2106410 | Open issues on the CSI-RS based measurement requirements | Nokia, Nokia Shanghai Bell |
| R4-2106459 | Discussion about CSI-RS L3 measurement | Intel Corporation |
| R4-2106525 | On the remaining issues of CSI-RS based L3 measurement | OPPO |
| R4-2106614 | Remaining issues on CSI-RS L3 measurement core requirements | vivo |
| R4-2106620 | Draft CR to 38.133 Correction on core requirements for CSI-RS based measurement | vivo |
| R4-2106926 | Discussion on remaining issues for CSI-RS based L3 measurement | Huawei, HiSilicon |
| R4-2106927 | CR on CSI-RS based intra-frequency scheduling restriction | Huawei, HiSilicon |
| R4-2106928 | CR on CSI-RS measurement window and intra-frequency measurements | Huawei, HiSilicon |
| R4-2106929 | Adding intra-frequency CSI-RS measurement in CSSF | Huawei, HiSilicon |
| R4-2107218 | Remaining issues of CSI-RS L3 core requirements | Qualcomm CDMA Technologies |
| R4-2107365 | Remaining issues of CSI-RS L3 core requirements | Qualcomm CDMA Technologies |
| 5.7.2 | RRM perf. requirements (38.133) | |
| R4-2105769 | WF on performance requirements of CSI-RS based L3 measurement | CATT, OPPO |
| R4-2105771 | Draft Big CR: Introduction of Rel-16 CSI-RS based L3 measurement RRM performance requirements | CATT, OPPO |
| 5.7.2.1 | General | |
| R4-2106411 | Discussion on the performance of CSI-RS based measurements | Nokia, Nokia Shanghai Bell |
| R4-2106615 | Further discussion on accuracy requirements for CSI-RS based measurement | vivo |
| 5.7.2.2.1 | CSI-RSRP requirements | |
| R4-2104577 | CSI-RSRP measurement accuracy requirement | MediaTek inc. |
| R4-2104735 | Discussion on performance requirement for CSI-RSRP | CATT |
| R4-2104737 | draft CR on performance requirement for CSI-RSRP | CATT |
| R4-2104937 | Simulation results for CSI-RSRP | CMCC |
| R4-2104940 | Discussion on CSI-RSRP measurement accuracy | CMCC |
| R4-2105775 | draft CR on performance requirement for CSI-RSRP | CATT |
| R4-2105777 | 38.133 draftCR on the CSI-RSRP accuracy requirements | Nokia, Nokia Shanghai Bell |
| R4-2106412 | 38.133 draftCR on the CSI-RSRP accuracy requirements | Nokia, Nokia Shanghai Bell |
| R4-2106526 | Simulation results for CSI-RS RSRP accuracy requirements | OPPO |
| R4-2106616 | Updated simulation results for CSI-RSRP measurement accuracy | vivo |
| R4-2107023 | Discussion on CSI-RSRP accuracy requirements | Huawei, HiSilicon |
| R4-2107214 | Updated simulation results for CSI-RSRP measurement | Qualcomm CDMA Technologies |
| 5.7.2.2.2 | CSI-RSRQ requirements | |
| R4-2104738 | draft CR on performance requirement for CSI-RSRQ | CATT |
| R4-2104938 | Simulation results for CSI-RSRQ | CMCC |
| R4-2104941 | Discussion on CSI-RSRQ measurement accuracy | CMCC |
| R4-2105776 | draft CR on performance requirement for CSI-RSRQ | CATT |
| R4-2106527 | Simulation results for CSI-RS RSRQ accuracy requirements | OPPO |
| R4-2106617 | Updated simulation results for CSI-RSRQ measurement accuracy | vivo |
| 5.7.2.2.3 | CSI-SINR requirements | |
| R4-2104578 | CSI-SINR measurement accuracy requirement | MediaTek inc. |
| R4-2104736 | Discussion on performance requirement for CSI-SINR | CATT |
| R4-2104739 | draft CR on performance requirement for CSI-SINR | CATT |
| R4-2104942 | Discussion on side condition for CSI-SINR measurement | CMCC |
| R4-2105778 | draftCR on CSI-SINR accuracy requirements | Huawei, HiSilicon |
| R4-2106528 | Discussion and simulation results for CSI-RS SINR accuracy requirements | OPPO |
| R4-2106618 | Updated simulation results for CSI-SINR measurement accuracy | vivo |
| R4-2106619 | Further iscussion on CSI-SINR measurement accuracy requirements | vivo |
| R4-2107024 | Discussion on CSI-SINR accuracy requirements | Huawei, HiSilicon |
| R4-2107025 | draftCR on CSI-SINR accuracy requirements | Huawei, HiSilicon |
| R4-2107215 | Updates on simulation results for CSI-SINR measurement | Qualcomm CDMA Technologies |
| 5.7.2.3 | Test cases | |
| R4-2105683 | Email discussion summary for [98-bis-e][213] NR_CSIRS_L3meas_2 | Moderator (OPPO) |
| R4-2105815 | Email discussion summary for [98-bis-e][213] NR_CSIRS_L3meas_2 | Moderator (OPPO) |
| 5.7.2.3.1 | General | |
| R4-2106529 | Discussion on remaining issues for CSI-RS L3 measurement tests | OPPO |
| 5.7.2.3.2 | Intra-frequency measurement | |
| R4-2104740 | draft CR on test case for intra-frequency CSI-RS based measurement | CATT |
| R4-2105779 | draft CR on test case for intra-frequency CSI-RS based measurement | CATT |
| R4-2105780 | 38.133 CR on the test case of EN-DC event triggered reporting for intra-frequency CSI-RS based measurements in FR1 | Nokia, Nokia Shanghai Bell |
| R4-2105781 | Updated CR on CSI-RS based L3 measurement RRM test cases | OPPO |
| R4-2105782 | Draft test case of CSI-RS based intra-frequency test for EN-DC event triggered reporting tests without gap for NR neighbor cell in FR2 | Qualcomm CDMA Technologies |
| R4-2106413 | 38.133 CR on the test case of EN-DC event triggered reporting for intra-frequency CSI-RS based measurements in FR1 | Nokia, Nokia Shanghai Bell |
| R4-2106530 | Updated CR on CSI-RS based L3 measurement RRM test cases | OPPO |
| R4-2107172 | Draft test case of CSI-RS based intra-frequency test for EN-DC event triggered reporting tests without gap for NR neighbor cell in FR2 | Qualcomm CDMA Technologies |
| 5.7.2.3.3 | Inter-frequency measurement | |
| R4-2105783 | Draft CR to 38.133 on SA event triggered reporting tests with gap for NR neighbor cell in FR2 | vivo |
| R4-2106623 | Draft CR to 38.133 on SA event triggered reporting tests with gap for NR neighbor cell in FR2 | vivo |
| 5.7.2.3.4 | Measurement performance | |
| R4-2104579 | Draft CR to update timing offset in test case for CSI-SINR in SA FR2 | MediaTek inc. |
| R4-2106414 | 38.133 CR on the TC of CSI-RSRP accuracy requirement in EN-DC in FR1 | Nokia, Nokia Shanghai Bell |
| R4-2106621 | Draft CR to 38.133 on test cases for EN-DC CSI-SINR measurement accuracy | vivo |
| R4-2106622 | Draft CR to 38.133 on CSI-RSRQ measurement accuracy for NR neighbor cell in FR2 | vivo |
| R4-2107026 | draft CR to update TC3 and TC12 for CSI-RS accuracy test | Huawei, HiSilicon |
| R4-2107173 | Draft test case of measurement performance for EN-DC CSI-RSRP measurement accuracy for NR neighbor cell in FR2 | Qualcomm CDMA Technologies |
| 5.8 | R16 NR maintenance | |
| R4-2105018 | Draft CR on spurious emission between n40 and n41 into Rel-16 TS 38.101-1 | CMCC,Huawei, HiSilicon, ZTE, OPPO,CATT |
| R4-2105019 | Draft CR on spurious emission between n40 and n41 into Rel-17 TS 38.101-1 | CMCC,Huawei, HiSilicon,ZTE, OPPO, CATT |
| R4-2105331 | Way forward on MPR evaluation for NR TxD & UL-MIMO | vivo, Skyworks |
| R4-2106672 | Discussion on spurious emission about UE co-existence between band n40 and n41 | Huawei, HiSilicon |
| 5.8.1 | Transmit diversity and power class related to UL MIMO | |
| R4-2105174 | Email discussion summary for [98-bis-e][101] NR_TxD | Moderator (vivo) |
| R4-2105330 | Way forward on NR TxD & Power Class | vivo |
| R4-2105440 | Email discussion summary for [98-bis-e][101] NR_TxD | Moderator (vivo) |
| 5.8.1.1 | R16 support of transmit diversity | |
| R4-2104485 | Remaining issues on NR transparent TxD | ZTE Wistron Telecom AB |
| R4-2104538 | Remaining issues in Transparent Tx Diversity | vivo |
| R4-2105082 | Requirements for transparent TxD | Ericsson |
| R4-2106558 | R16 TxD testing issues | OPPO |
| R4-2107112 | Discussion on FR1 Tx Diversity EVM measurements | Rohde & Schwarz |
| R4-2107283 | TxD MPR and SRS ant switching | Qualcomm Incorporated |
| R4-2107306 | On remaining issues for TxD | Huawei, HiSilicon |
| R4-2107307 | draft CR for TS 38.101-1 Tx diversity requirements | Huawei, HiSilicon, vivo, OPPO |
| R4-2107367 | On the EVM Definition for Transmit Diversity and Single Layer Transmission | Motorola Mobility España SA |
| R4-2107368 | On the EVM Definition for Transmit Diversity and Single Layer Transmission | Motorola Mobility España SA |
| R4-2107369 | On the EVM Definition for Transmit Diversity and Single Layer Transmission | Lenovo, Motorola Mobility |
| 5.8.1.2 | Power class related to UL MIMO and other related req. (MPR, SEM, etc) | |
| R4-2104486 | Discussion on power class related issues and the corresponding reply LS | ZTE Wistron Telecom AB |
| R4-2104487 | Draft CR on resolving NR power class ambiguity issue for an intra-band PC2 EN-DC UE | ZTE Wistron Telecom AB |
| R4-2104539 | Remaining issues in Power class & UL MIMO related requirments | vivo |
| R4-2105083 | NSA power class for Rel-15, its verification, applicability of TxD and power fall-back of SA UL-MIMO. | Ericsson |
| R4-2105084 | Correction of Pcmax for an NR PC2 UE supporting NR PC3 for EN-DC | Ericsson |
| R4-2106368 | Draft CR to TS38.101-1: Correction on frequency separation classes and configured transmitted power for NR non-contiguous CA | ZTE Corporation |
| R4-2106369 | Draft CR to TS38.101-1: Correction on frequency separation classes and configured transmitted power for NR non-contiguous CA | ZTE Corporation |
| R4-2106370 | Draft CR to TS38.101-1: Add missing CA_n1A-n3A-n78A | ZTE Corporation |
| R4-2106371 | Draft CR to TS38.101-1: Add missing CA_n1A-n3A-n78A | ZTE Corporation, China Telecom |
| R4-2106372 | Draft CR to TS38.101-2: Some Corrections on for CA_n260-n261 | ZTE Corporation, Verizon |
| R4-2106373 | Draft CR to TS38.101-2: Some Corrections on for CA_n260-n261 | ZTE Corporation, Verizon |
| R4-2106546 | Draft CR for 38.101-1 Rel16 corrections on power tolerance for intra-band contiguous CA | Xiaomi |
| R4-2106547 | Draft CR for 38.101-1 Rel17 corrections on power tolerance for intra-band contiguous CA | Xiaomi |
| R4-2106903 | Draft CR for TS 38.101-1: Intra-band UL CA power class corrections | Apple |
| R4-2107113 | Discussion on FR1 UL MIMO EVM measurements | Rohde & Schwarz |
| R4-2107285 | Handling power class ambiguity | Qualcomm Incorporated |
| R4-2107308 | Discussion and draft reply LS on EN-DC power class | Huawei, HiSilicon |
| R4-2107309 | draft CR for TS 38.101-3 Correction on EN-DC power class | Huawei, HiSilicon |
| R4-2107336 | MPR for PC1.5 compared to 2Tx PC2 | T-Mobile USA |
| 5.8.2 | NR-DC Cell-grouping UE capability | |
| R4-2104488 | Discussion on reply LS to RAN2 on cell grouping capability for NR DC | ZTE Wistron Telecom AB |
| R4-2105175 | Email discussion summary for [98-bis-e][102] NR_LTE_NR_DC_CA_enh | Moderator (Ericsson) |
| R4-2105333 | Reply LS on Introduction of Cell Grouping UE capability for NR-DC | Qualcomm Incorporated |
| R4-2105441 | Email discussion summary for [98-bis-e][102] NR_LTE_NR_DC_CA_enh | Moderator (Ericsson) |
| R4-2106670 | Discussion and draft Reply LS on cell grouping UE capability for NR-DC | Huawei, HiSilicon |
| R4-2107355 | Reply LS on Introduction of Cell Grouping UE capability for NR-DC | Qualcomm Incorporated |
| 6 | Rel-16 UE feature list | |
| R4-2104858 | On R16 NR HST UE capabilitiesOn R16 NR HST UE capabilities | Apple |
| R4-2105176 | Email discussion summary for [98-bis-e][103] R16_UE_ feature | Moderator (CMCC) |
| R4-2105442 | Email discussion summary for [98-bis-e][103] R16_UE_ feature | Moderator (CMCC) |
| R4-2105831 | WF on NR HST UE capabilities | CMCC |
| R4-2105832 | Rel-16 UE feature list | CMCC |
| R4-2105833 | LS on RAN4 UE feature list | CMCC |
| R4-2105853 | WF on NR HST UE capabilities | CMCC |
| R4-2105854 | Rel-16 UE feature list | CMCC |
| R4-2105855 | LS on RAN4 UE feature list | CMCC |
| R4-2106442 | Discussion on UE capabilities | Intel Corporation |
| R4-2106989 | Discussion on per-FR gap capability | Huawei, HiSilicon |
| R4-2107272 | On intrabandENDC-support IE | HiSilicon Technologies Co. Ltd |
| 7.1 | NR intra band Carrier Aggregation for xCC DL/yCC UL including contiguous and non-contiguous spectrum (x>=y) | |
| R4-2105177 | Email discussion summary for [98-bis-e][104] NR_Baskets_Part_1 | Moderator (Nokia) |
| 7.1.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106696 | Revised WID NR Intra-band Rel-17 | Ericsson |
| R4-2106699 | CR 38.101-1 introduction completed band combinations Rel-17 NR Intra-band | Ericsson |
| R4-2106700 | CR 38.101-2 introduction completed band combinations Rel-17 NR Intra-band | Ericsson |
| R4-2106704 | TR 38.717-01-01 v0.4.0 Rel-17 NR Intra-band | Ericsson |
| 7.1.2 | UE RF for FR1 | |
| R4-2104416 | draft CR to 38.101-1: CA_n66(2A) and CA_n(3A) | Nokia, AT&T |
| R4-2104479 | Draft CR to TS 38.101-1 – Adding BCS’es with 30MHz for n48 Intra-band CA | DISH Network |
| R4-2105048 | Draft CR for 38.101-1 to introduce BCS2 to CA_n41C and CA_n41(2A) | Samsung, KDDI |
| R4-2105289 | draft CR to 38.101-1: CA_n66(2A) and CA_n(3A) | Nokia, AT&T |
| R4-2106648 | Updated TP for TR 38.717-01-01: CA_n77(3A)_BCS1 | Huawei, HiSilicon |
| R4-2107357 | Intraband UL CA for NR-U | Qualcomm Incorporated |
| 7.1.3 | UE RF for FR2 | |
| R4-2106724 | draft CR 38.101-2 to include new CA configurations n258 | Ericsson, US Cellular |
| 7.2 | NR inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1, 2) | |
| R4-2105178 | Email discussion summary for [98-bis-e][105] NR_Baskets_Part_2 | Moderator (Nokia) |
| 7.2.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2104913 | TR 38.717-02-01 v0.4.0 | ZTE Wistron Telecom AB |
| 7.2.2 | NR inter band CA without any FR2 band(s) | |
| R4-2104412 | TP to TR 38.717-02-01: CA_n12-n77 | Nokia, AT&T |
| R4-2104413 | TP to TR 38.717-02-01: CA_n14-n77 | Nokia, AT&T |
| R4-2104414 | TP to TR 38.717-02-01: CA_n30-n77 | Nokia, AT&T |
| R4-2104415 | draft CR to 38.101-1: CA_n2-n77 | Nokia, AT&T |
| R4-2104417 | draft CR to 38.101-1: CA_n5A-n77(2A) introduction of UL CA_n77(2A) | Nokia, AT&T |
| R4-2104418 | TP to TR 38.717-02-01: CA_n25A-n71(2A) | Nokia, T-Mobile USA |
| R4-2104419 | TP to TR 38.717-02-01: CA_n41(2A)-n66A | Nokia, T-Mobile USA |
| R4-2104423 | TP to TR 38.717-02-01: CA_n25-n48 combinations | Nokia, T-Mobile USA |
| R4-2104454 | draft CR adding new DC_n46-n48 configurations | Charter Communications, Inc |
| R4-2104507 | DraftCR for NR inter band CA DC combinations for 2DL with up to 2 bands UL | Verizon Denmark |
| R4-2104640 | TP for TR 38.717-02-01: CA_n1-n20 | VODAFONE Group Plc |
| R4-2104641 | TP for TR 38.717-02-01: CA_n3-n20 | VODAFONE Group Plc |
| R4-2104642 | TP for TR 38.717-02-01: CA_n8-n20 | VODAFONE Group Plc |
| R4-2104910 | Draft CR for TS 38.101-1: Support of n77(2A) in CA_n77-n79 | SoftBank Corp. |
| R4-2104911 | Draft CR for TS 38.101-1: Support of DC_n3-n79, DC_n28-n79 and DC_n77-n79 | SoftBank Corp. |
| R4-2105055 | TP for TR 38.717-02-01: CA_n1-n18 | Samsung, KDDI |
| R4-2105056 | TP for TR 38.717-02-01: CA_n1-n74 | Samsung, KDDI |
| R4-2105057 | TP for TR 38.717-02-01: CA_n18-n74 | Samsung, KDDI |
| R4-2105058 | TP for TR 38.717-02-01: CA_n18-n77 | Samsung, KDDI |
| R4-2105059 | TP for TR 38.717-02-01: CA_n18-n78 | Samsung, KDDI |
| R4-2105060 | TP for TR 38.717-02-01: CA_n40-n77 | Samsung, KDDI |
| R4-2105061 | TP for TR 38.717-02-01: CA_n74-n78 | Samsung, KDDI |
| R4-2105062 | TP for TR 38.717-02-01: CA_n1-n41 | Samsung, KDDI |
| R4-2105063 | TP for TR 38.717-02-01: CA_n3-n41 | Samsung, KDDI |
| R4-2105064 | TP for TR 38.717-02-01: CA_n3-n74 | Samsung, KDDI |
| R4-2105065 | TP for TR 38.717-02-01: CA_n18-n28 | Samsung, KDDI |
| R4-2105066 | TP for TR 38.717-02-01: CA_n28-n74 | Samsung, KDDI |
| R4-2105067 | TP for TR 38.717-02-01: CA_n41-n74 | Samsung, KDDI |
| R4-2105068 | TP for TR 38.717-02-01: CA_n74-n77 | Samsung, KDDI |
| R4-2105236 | TP to TR 38.717-02-01: CA_n12-n77 | Nokia, AT&T |
| R4-2105237 | TP to TR 38.717-02-01: CA_n14-n77 | Nokia, AT&T |
| R4-2105238 | TP to TR 38.717-02-01: CA_n30-n77 | Nokia, AT&T |
| R4-2105239 | draft CR to 38.101-1: CA_n2-n77 | Nokia, AT&T |
| R4-2105240 | draft CR to 38.101-1: CA_n5A-n77(2A) introduction of UL CA_n77(2A) | Nokia, AT&T |
| R4-2105241 | TP to TR 38.717-02-01: CA_n25A-n71(2A) | Nokia, T-Mobile USA |
| R4-2105242 | TP to TR 38.717-02-01: CA_n41(2A)-n66A | Nokia, T-Mobile USA |
| R4-2105243 | TP to TR 38.717-02-01: CA_n25-n48 combinations | Nokia, T-Mobile USA |
| R4-2105245 | DraftCR for NR inter band CA DC combinations for 2DL with up to 2 bands UL | Verizon |
| R4-2105246 | TP for TR 38.717-02-01: CA_n1-n74 | Samsung,KDDI |
| R4-2105247 | TP for TR 38.717-02-01: CA_n18-n77 | Samsung, KDDI |
| R4-2105248 | TP for TR 38.717-02-01: CA_n18-n78 | Samsung, KDDI |
| R4-2105249 | TP for TR 38.717-02-01: CA_n40-n77 | Samsung,KDDI |
| R4-2105250 | TP for TR 38.717-02-01: CA_n1-n41 | Samsung, KDDI |
| R4-2105251 | TP for TR 38.717-02-01: CA_n3-n41 | Samsung,KDDI |
| R4-2105252 | TP for TR 38.717-02-01: CA_n3-n74 | Samsung, KDDI |
| R4-2105253 | TP for TR 38.717-02-01: CA_n18-n28 | Samsung, KDDI |
| R4-2105254 | TP for TR 38.717-02-01: CA_n28-n74 | Samsung, KDDI |
| R4-2105255 | TP for TR 38.717-02-01: CA_n74-n77 | Samsung, KDDI |
| R4-2105256 | TP for TR 38.717-02-01: CA_n13-n77 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2105257 | TP for TR 38.717-02-01: CA_n2-n7 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2105258 | TP for TR 38.717-02-01: CA_n24-n41 | Ligado Networks, Huawei, HiSilicon |
| R4-2105259 | TP for TR 38.717-02-01: CA_n24-n48 | Ligado Networks, Huawei, HiSilicon |
| R4-2105260 | TP for TR 38.717-02-01: CA_n24-n77 | Ligado Networks, Huawei HiSilicon |
| R4-2105261 | TP for TR 38.717-02-01: CA_n3A-n39A | Huawei, HiSilicon |
| R4-2105262 | TP for TR 38.717-02-01: CA_n28A-n71A | Huawei, HiSilicon |
| R4-2105263 | TP for TR 38.717-02-01 to include CA_n2A-n30A, CA_n2(2A)-n30A | Ericsson, AT&T |
| R4-2105264 | TP for TR 38.717-02-01 to include CA_n5A-n30A, UL CA_n2A-n30A | Ericsson, AT&T |
| R4-2105265 | draft CR 38.101-1 to include new CA configurations n2-n5, n2-n66, n5-n66 | Ericsson, AT&T |
| R4-2105266 | TP for TR 38.717-02-01 to include new BCS's and UL configurations n25-n71 | Ericsson, T-Mobile US |
| R4-2105267 | TP for TR 38.717-02-01 to include new BCS's and UL configurations n41-n66 | Ericsson, T-Mobile US |
| R4-2105268 | TP for TR 38.717-02-01 to include new BCS's and UL configurationsn41A-n71 | Ericsson, T-Mobile US |
| R4-2105269 | TP for TR 38.717-02-01 to include new BCS's and UL configurations n66-n71 | Ericsson, T-Mobile US |
| R4-2105270 | TP to TR 38.717-02-01: Addition of CA_48-53 | Nokia, Globalstar |
| R4-2105271 | DraftCR for FR2 inter-band CA | Verizon |
| R4-2105324 | TP for TR 38.717-02-01: CA_n34A-n40A | ZTE Corporation |
| R4-2106382 | TP for TR 38.717-02-01: CA_n34A-n40A | ZTE Corporation |
| R4-2106491 | TP for TR 38.717-02-01: CA_n13-n77 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106492 | TP for TR 38.717-02-01: CA_n2-n7 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106493 | DraftCR for 38.101-1 to add additional combinations for CA_n2-n66 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106494 | DraftCR for 38.101-1 to add additional combinations for CA_n25-n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106572 | TP for TR 38.717-02-01: CA_n24-n41 | Ligado Networks |
| R4-2106585 | TP for TR 38.717-02-01: CA_n24-n48 | Ligado Networks |
| R4-2106586 | TP for TR 38.717-02-01: CA_n24-n77 | Ligado Networks |
| R4-2106649 | TP for TR 38.717-02-01: CA_n3A-n39A | Huawei, HiSilicon |
| R4-2106650 | TP for TR 38.717-02-01: CA_n28A-n71A | Huawei, HiSilicon |
| R4-2106651 | Draft CR for 38.101-1 to correct the configuration table for two bands NR CA | Huawei, HiSilicon |
| R4-2106715 | TP for TR 38.717-02-01 to include CA_n2A-n30A, CA_n2(2A)-n30A | Ericsson, AT&T |
| R4-2106716 | TP for TR 38.717-02-01 to include CA_n5A-n30A, UL CA_n2A-n30A | Ericsson, AT&T |
| R4-2106717 | TP for TR 38.717-02-01 to include CA_n30A-n66A, CA_n30A-n66(2A), CA_n30A-n66(3A), UL CA_n30A-n66A | Ericsson, AT&T |
| R4-2106722 | draft CR 38.101-1 to include new CA configurations n2-n5, n2-n66, n5-n66 | Ericsson, AT&T |
| R4-2106772 | TP for TR 38.717-02-01 to include new BCS's and UL configurations n25-n71 | Ericsson, T-Mobile US |
| R4-2106773 | TP for TR 38.717-02-01 to include new BCS's and UL configurations n41-n66 | Ericsson, T-Mobile US |
| R4-2106774 | TP for TR 38.717-02-01 to include new BCS's and UL configurationsn41A-n71 | Ericsson, T-Mobile US |
| R4-2106775 | TP for TR 38.717-02-01 to include new BCS's and UL configurations n66-n71 | Ericsson, T-Mobile US |
| R4-2107200 | TP to TR 38.717-02-01 Addition of CA_48-53 | Nokia, Globalstar |
| 7.2.3 | NR inter band CA with at least one FR2 band | |
| R4-2104508 | DraftCR for FR2 inter-band CA | Verizon Denmark |
| R4-2105049 | Draft CR for 38.101-3 to introduce new configurations of DC_n3-n257, DC_n41-n257 and DC_n78-n257 | Samsung, KDDI |
| R4-2106495 | DraftCR for 38.101-3 to add CA_n66A-n260M BCS1 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106756 | draft CR 38.101-3 to include new CA configurations and new BCS's n1-n258 and n78-n258 | Ericsson, Telstra |
| R4-2106759 | TP for TR 38.717-02-01 to include CA_n3A-n258A/B/C/D/E/F/G/H/I/J/K/L/M, UL CA_n3A-n258A | Ericsson, Telstra |
| R4-2106760 | TP for TR 38.717-02-01 to include CA_n7A/B-n258A/B/C/D/E/F/G/H/I/J/K/L/M, UL CA_n7A-n258A/G/H/I/ | Ericsson, Telstra |
| R4-2107042 | draft CR for CA_n1A-n257J/K/L/M with uplink CA support up to CA_n1A-n257K | CHTTL |
| 7.3.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106888 | TR 37.717-11-11 v0.4.0 Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) | CHTTL |
| R4-2106913 | Revised WID for Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) | CHTTL |
| R4-2106917 | Big draft CR for Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) | CHTTL |
| 7.3.2 | EN-DC without FR2 band | |
| R4-2104407 | TP to TR 37.717-11-11: DC_2A_n30A | Nokia, AT&T |
| R4-2104408 | TP to TR 37.717-11-11: DC_5A_n30A | Nokia, AT&T |
| R4-2104409 | TP to TR 37.717-11-11: DC_12A_n30A | Nokia, AT&T |
| R4-2104410 | TP to TR 37.717-11-11: DC_66A_n30A | Nokia, AT&T |
| R4-2104425 | TP to TR 37.717-11-11: DC_71A_n71A | Nokia, T-Mobile USA |
| R4-2104506 | DraftCR for Rel-17 Dual Connectivity (DC) of 1LTE band and 1NR band (1DL/1UL) | Verizon Denmark |
| R4-2105050 | TP for TR 37.717-11-11: DC_11_n41 | Samsung, KDDI |
| R4-2105069 | TP for TR 37.717-11-11: DC_66_n66 | Samsung, TELUS, Bell mobility |
| R4-2105285 | TP to TR 37.717-11-11: DC_2A_n30A | Nokia, AT&T |
| R4-2105286 | TP to TR 37.717-11-11: DC_5A_n30A | Nokia, AT&T |
| R4-2105287 | TP to TR 37.717-11-11: DC_12A_n30A | Nokia, AT&T |
| R4-2105288 | TP to TR 37.717-11-11: DC_66A_n30A | Nokia, AT&T |
| R4-2105290 | TP to TR 37.717-11-11: DC_71A_n71A | Nokia, T-Mobile USA |
| R4-2105296 | TP for TR 37.717-11-11: DC_11_n41 | Samsung, KDDI |
| R4-2105298 | TP for TR 37.717-11-11: DC_66_n66 | Samsung, TELUS, Bell mobility |
| R4-2105307 | TP for TR 37.717-11-11: DC_38A_n28A | Huawei, HiSilicon |
| R4-2105308 | TP for TR 37.717-11-11 to include DC_12_n77 | Ericsson, AT&T |
| R4-2105309 | TP for TR 37.717-11-11 to include DC_14_n77 | Ericsson, AT&T |
| R4-2105310 | TP for TR 37.717-11-11 to include DC_30_n77 | Ericsson, AT&T |
| R4-2105311 | TP for TR 37.717-11-11 to include DC_14_n30 | Ericsson, AT&T |
| R4-2105316 | draft CR 38.101-3 to include new DC configuration 8_n78 | Ericsson, Telefonica |
| R4-2105317 | TP for TR 37.717-11-11 to include DC_2_n25 | Ericsson, Bell Mobility |
| R4-2105318 | TP for TR 37.717-11-11 to include DC_7_n25 | Ericsson, Bell Mobility |
| R4-2106638 | TP for TR 37.717-11-11: DC_38A_n28A | Huawei, HiSilicon |
| R4-2106707 | TP for TR 37.717-11-11 to include DC_12_n77 | Ericsson, AT&T |
| R4-2106708 | TP for TR 37.717-11-11 to include DC_14_n77 | Ericsson, AT&T |
| R4-2106709 | TP for TR 37.717-11-11 to include DC_30_n77 | Ericsson, AT&T |
| R4-2106710 | TP for TR 37.717-11-11 to include DC_14_n30 | Ericsson, AT&T |
| R4-2106727 | draft CR 38.101-3 to include new DC configuration 8_n78 | Ericsson, Telefonica |
| R4-2106733 | TP for TR 37.717-11-11 to include DC_2_n25 | Ericsson, Bell Mobility |
| R4-2106734 | TP for TR 37.717-11-11 to include DC_7_n25 | Ericsson, Bell Mobility |
| R4-2106735 | TP for TR 37.717-11-11 to include DC_13_n25 | Ericsson, Bell Mobility |
| R4-2106919 | TP for TR 37.717-11-11: support of DC_3-3_n8, DC_7-7_n8 | CHTTL |
| R4-2107326 | Impact of n40 large CBW on DC_1_n40 | Skyworks Solutions Inc. |
| R4-2107338 | Intra-band REFSENS Exceptions for n71 | Skyworks Solutions Inc. |
| 7.3.3 | EN-DC with FR2 band | |
| R4-2106639 | TP for TR 37.717-11-11: DC_20_n257 | Huawei, HiSilicon, Telecom Italia |
| R4-2106640 | Draft CR for 38.101-3 to introduce DC_20_n258 | Huawei, HiSilicon, Telecom Italia |
| R4-2106725 | draft CR 38.101-3 new configurations for 2_n261, 12_n261, 66_n261 | Ericsson, US Cellular |
| R4-2107201 | draft CR to add 2A_n260D-E to 38.101-3 | Nokia, U.S. Cellular |
| R4-2107202 | draft CR to add 12A_n260D-Q to 38.101-3 | Nokia, U.S. Cellular |
| 7.4.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106490 | TR 37.717-21-11 V0.4.0 for DC of 2 LTE band and 1 NR band | Huawei, HiSilicon |
| 7.4.2 | EN-DC without FR2 band | |
| R4-2104406 | TP to TR 37.717-21-11: DC_20-40_n1 | Nokia, Telefonica |
| R4-2104411 | TP to TR 37.717-21-11: DC_5A-30A_n2A | Nokia, AT&T |
| R4-2104721 | draft CR for DC_2-5_n77, DC_2-13_n77, DC_2-48-n77, DC_2-66_n77, DC_13-66_n77 to TS 38.101-3 | Nokia, Nokia Shanghai Bell |
| R4-2104722 | TP to TR 37.717-21-11 DC_2-46_n77 | Nokia, Nokia Shanghai Bell |
| R4-2104723 | TP to TR 37.717-21-11 DC_13-46_n77 | Nokia, Nokia Shanghai Bell |
| R4-2104724 | TP to TR 37.717-21-11 DC_46-66_n77 | Nokia, Nokia Shanghai Bell |
| R4-2105051 | TP for TR 37.717-21-22: DC_1-11_n41 | Samsung, KDDI |
| R4-2105292 | draft CR for DC_2-5_n77, DC_2-13_n77, DC_2-48-n77, DC_2-66_n77, DC_13-66_n77 to TS 38.101-3 | Nokia, Nokia Shanghai Bell, [Verizon] |
| R4-2105293 | TP to TR 37.717-21-11 DC_2-46_n77 | Nokia, Nokia Shanghai Bell, [Verizon] |
| R4-2105294 | TP to TR 37.717-21-11 DC_13-46_n77 | Nokia, Nokia Shanghai Bell, [Verizon] |
| R4-2105295 | TP to TR 37.717-21-11 DC_46-66_n77 | Nokia, Nokia Shanghai Bell, [Verizon] |
| R4-2105297 | TP for TR 37.717-21-11: DC_1-11_n41 | Samsung, KDDI |
| R4-2105306 | TP for TR 37.717-21-11: DC_2-12_n7 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2105312 | TP for TR 37.717-21-11 to include 14-30_n66 | Ericsson, AT&T |
| R4-2105313 | TP for TR 37.717-21-11 to include 2-(n)5 | Ericsson, AT&T |
| R4-2105314 | TP for TR 37.717-21-11 to include 30-(n)5 | Ericsson, AT&T |
| R4-2105315 | TP for TR 37.717-21-11 to include 28-40_n78 | Ericsson, Telefonica |
| R4-2105319 | TP to TR 37.717-21-11 Addition of DC_13-46_n66 | Nokia, Verizon |
| R4-2105320 | TP to TR 37.717-21-11 Addition of DC_46-48_n66 | Nokia, Verizon |
| R4-2105321 | TP to TR 37.717-21-11 Addition of DC_2-46_n5 | Nokia, Verizon |
| R4-2105322 | TP to TR 37.717-21-11 Addition of DC_46-48_n5 | Nokia, Verizon |
| R4-2105327 | TP for TR 37.717-21-11: DC_1-11_n41 | Samsung, KDDI |
| R4-2106498 | TP for TR 37.717-21-11: DC_2-12_n7 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106499 | TP for TR 37.717-21-11: DC_5A-7A-7A_n66a | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106500 | TP for TR 37.717-21-11: DC_2-5_n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106501 | TP for TR 37.717-21-11: DC_2A-12A_n78(2A) | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106502 | TP for TR 37.717-21-11: DC_7-29_n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106641 | TP for TR 37.717-21-11: DC_1A-38A_n28A | Huawei, HiSilicon |
| R4-2106642 | TP for TR 37.717-21-11: DC_3A-38A_n28A/ DC_3C-38A_n28A | Huawei, HiSilicon |
| R4-2106711 | TP for TR 37.717-21-11 to include 14-30_n66 | Ericsson, AT&T |
| R4-2106712 | TP for TR 37.717-21-11 to include 14-30_n2 | Ericsson, AT&T |
| R4-2106713 | TP for TR 37.717-21-11 to include 2-(n)5 | Ericsson, AT&T |
| R4-2106714 | TP for TR 37.717-21-11 to include 30-(n)5 | Ericsson, AT&T |
| R4-2106726 | TP for TR 37.717-21-11 to include 28-40_n78 | Ericsson, Telefonica |
| R4-2106728 | draft CR 38.101-3 to include new configurations for DC_3-20_n78 | Ericsson, Telefonica |
| R4-2106736 | TP for TR 37.717-21-11 to include 2-7_n25 | Ericsson, Bell Mobility |
| R4-2106737 | TP for TR 37.717-21-11 to include 2-13_n25 | Ericsson, Bell Mobility |
| R4-2106738 | TP for TR 37.717-21-11 to include 2-66_n25 | Ericsson, Bell Mobility |
| R4-2106739 | TP for TR 37.717-21-11 to include DC_7-13_n25 | Ericsson, Bell Mobility |
| R4-2106740 | TP for TR 37.717-21-11 to include DC_7-66_n25 | Ericsson, Bell Mobility |
| R4-2106754 | draft CR 38.101-3 to include new configurations for DC_2-7_n66 | Ericsson, Bell Mobility |
| R4-2106761 | TP for TR 37.717-21-11 to include 3-7_n3 | Ericsson, Telstra |
| R4-2106762 | TP for TR 37.717-21-11 to include 3-28_n3 | Ericsson, Telstra |
| R4-2106925 | TP for TR 37.717-21-11: support of DC_3-3-7_n8, DC_3-7-7_n8, DC_3-3-7-7_n8 | CHTTL |
| R4-2107203 | TP to TR 37.717-21-11 Addition of DC_13-46_n66 | Nokia, Verizon |
| R4-2107204 | TP to TR 37.717-21-11 Addition of DC_46-48_n66 | Nokia, Verizon |
| R4-2107205 | draft CR to add DC_2A-46E_n66A to 38.101-3 | Nokia, Verizon |
| R4-2107206 | TP to TR 37.717-21-11 Addition of DC_2-46_n5 | Nokia, Verizon |
| R4-2107207 | TP to TR 37.717-21-11 Addition of DC_46-48_n5 | Nokia, Verizon |
| R4-2107208 | draft CR to add DC_13A-66A-66A_n5A to 38.101-3 | Nokia, Verizon |
| 7.4.3 | DMEN-DC with FR2 band | |
| R4-2104426 | draft CR to 38.101-3: DC_13-46-n261 addition of UL configurations | Nokia, Verizon |
| R4-2106723 | draft CR 38.101-3 to include new configurations for DC_2-66_n260 | Ericsson, AT&T |
| R4-2107044 | draft CR for DC_7-8_n257, DC_7-7-8_n257, DC_3-3-8_n257 | CHTTL |
| 7.5.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106697 | Revised WID LTE 3DL and one NR band Rel-17 | Ericsson |
| R4-2106701 | CR 38.101-3 introduction completed band combinations LTE 3DL and one NR band | Ericsson |
| R4-2106705 | TR 37.717-31-11 v0.4.0 Rel-17 DC combinations LTE 3DL and one NR band | Ericsson |
| 7.5.2 | EN-DC without FR2 band | |
| R4-2104403 | TP to TR 37.717-31-11: DC_1A-28A-40A_n78A | Nokia, Telefonica |
| R4-2104404 | TP to TR 37.717-31-11: DC_3A-28A-40A_n78A | Nokia, Telefonica |
| R4-2104711 | draft CR DC_5-7-7-66_n66 to TS 38.101-3 | Nokia, Nokia Shanghai Bell |
| R4-2104872 | CR to TS 38.101-3 on delta TIB correction | ZTE Corporation |
| R4-2104873 | CR to TS 38.101-3 on delta TIB correction (CAT A) | ZTE Corporation |
| R4-2105047 | Draft CR for 38.101-3 to introduce DC_1A-11A-18A_n77(2A) and DC_1A-11A-18A_n78(2A) | Samsung, KDDI |
| R4-2105052 | TP for TR 37.717-31-11: DC_1-11-18_n3 | Samsung, KDDI |
| R4-2105053 | TP for TR 37.717-31-11: DC_1-11-18_n28 | Samsung, KDDI |
| R4-2105054 | TP for TR 37.717-31-11: DC_1-11-18_n41 | Samsung, KDDI |
| R4-2105075 | TP for TR 37.717-31-11: DC_2-5-66_n48 | Samsung, Verizon |
| R4-2105076 | TP for TR 37.717-31-11: DC_2-13-48_n77 | Samsung, Verizon |
| R4-2105077 | TP for TR 37.717-31-11: DC_2-46-48_n2 | Samsung, Verizon |
| R4-2105078 | TP for TR 37.717-31-11: DC_2-48-66_n2 | Samsung, Verizon |
| R4-2105079 | TP for TR 37.717-31-11: DC_2-48-66_n66 | Samsung, Verizon |
| R4-2105080 | TP for TR 37.717-31-11: DC_13-48-66_n77 | Samsung, Verizon |
| R4-2105081 | Draft CR for 38.101-3 to introduce new configurations of DC_2-13-66_n66, DC_2-5-66_n66 and DC_2-48-66_n5 | Samsung, Verizon |
| R4-2105282 | TP to TR 37.717-31-11: DC_1A-28A-40A_n78A | Nokia, Telefonica |
| R4-2105283 | TP to TR 37.717-31-11: DC_3A-28A-40A_n78A | Nokia, Telefonica |
| R4-2105291 | draft CR DC_5A-7A-7A-66A_n66A to TS 38.101-3 | Nokia, Nokia Shanghai Bell, [TELUS, Bell Mobility] |
| R4-2105299 | TP for TR 37.717-31-11: DC_2-46-48_n2 | Samsung, Verizon |
| R4-2105300 | TP for TR 37.717-31-11: DC_2-48-66_n2 | Samsung, Verizon |
| R4-2105301 | TP for TR 37.717-31-11: DC_2-48-66_n66 | Samsung, Verizon |
| R4-2105302 | TP for TR 37.717-31-11: DC_13-48-66_n77 | Samsung, Verizon |
| R4-2105303 | Draft CR for 38.101-3 to introduce new configurations of DC_2-13-66_n66, DC_2-5-66_n66 and DC_2-48-66_n5 | Samsung, Verizon |
| R4-2105304 | TP for TR 37.717-31-11: DC_1A-3A-20A_n7A | ZTE Corporation |
| R4-2106379 | TP for TR 37.717-31-11: DC_1A-3A-20A_n7A | ZTE Corporation |
| R4-2106643 | TP for TR 37.717-31-11: DC_1A-3A-38A_n28A/ DC_1A-3C-38A_n28A | Huawei, HiSilicon |
| R4-2106644 | TP for TR 37.717-31-11: DC_1A-7A-38A_n28A | Huawei, HiSilicon |
| R4-2106645 | TP for TR 37.717-31-11: DC_3A-7A-38A_n28A/DC_3C-7A-38A_n28A | Huawei, HiSilicon |
| R4-2106741 | TP to TR TR 37.717-31-11 to include 2-7-13_n25 | Ericsson, Bell Mobility |
| R4-2106742 | TP to TR TR 37.717-31-11 to include DC_2-7-66_n25 | Ericsson, Bell Mobility |
| R4-2107051 | TP for TR 37 717-31-11 to include DC_2A-5A-30A_n2A | Ericsson, AT&T |
| R4-2107052 | TP for TR 37 717-31-11 to include DC_2A-5A-30A_n66A | Ericsson, AT&T |
| R4-2107053 | TP for TR 37 717-31-11 to include DC_2A-14A-30A_n2A | Ericsson, AT&T |
| R4-2107054 | TP for TR 37 717-31-11 to include DC_2A-29A-30A_n66A | Ericsson, AT&T |
| R4-2107056 | TP for TR 37 717-31-11 to include DC_2A-46D-66A_n5A | Ericsson, AT&T |
| R4-2107058 | TP for TR 37 717-31-11 to include DC_5A-30A-66A_n2A | Ericsson, AT&T |
| R4-2107059 | TP for TR 37 717-31-11 to include DC_5A-30A-66A_n66A | Ericsson, AT&T |
| R4-2107060 | TP for TR 37 717-31-11 to include DC_14A-30A-66A_n66A | Ericsson, AT&T |
| R4-2107061 | TP for TR 37 717-31-11 to include DC_14A-30A-66A-66A_n2A | Ericsson, AT&T |
| R4-2107063 | TP for TR 37 717-31-11 to include DC_2A-14A-30A_n66A | Ericsson, AT&T |
| R4-2107064 | TP for TR 37 717-31-11 to include DC_1A-3A-7A_n3A | Ericsson,Telstra |
| R4-2107065 | TP for TR 37 717-31-11 to include DC_1A-3A-28A_n3A | Ericsson,Telstra |
| R4-2107066 | TP for TR 37 717-31-11 to include DC_3A-7A-28A_n3A | Ericsson,Telstra |
| R4-2107075 | draft CR to 38.101-3 to add new configurations for 2-5-5-66_n66, 2-29-66_n66 and 2-30-66_n66 | Ericsson, AT&T |
| 7.5.3 | EN-DC with FR2 band | |
| R4-2106757 | draft CR 38.101-3 to include new configurations for DC_1-7_n3-n78 and DC_1-7-28_n3 | Ericsson, Telstra |
| R4-2107055 | TP for TR 37 717-31-11 to include DC_2A-29A-66A_n260M | Ericsson, AT&T |
| R4-2107057 | TP for TR 37 717-31-11 to include DC_2A-46D-66A_n260M | Ericsson, AT&T |
| R4-2107062 | TP for TR 37 717-31-11 to include DC_29A-30A-66A_n260M | Ericsson, AT&T |
| R4-2107074 | draft CR to 38.101-3 to add configurations for 2-30-66_n260 and 2-29-30_n260 | Ericsson, AT&T |
| 7.6.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2107188 | draft TR 37.717-41-11 v0.4.0 | Nokia, Nokia Shanghai Bell |
| 7.6.2 | EN-DC without FR2 band | |
| R4-2104405 | TP to TR 37.717-41-11: DC_1-3-28-40_n78 | Nokia, Telefonica |
| R4-2105284 | TP to TR 37.717-41-11: DC_1-3-28-40_n78 | Nokia, Telefonica |
| R4-2105305 | TP for TR 37.717-41-11_DC_1A-3A-7A-20A_n38A | ZTE Corporation |
| R4-2106380 | TP for TR 37.717-41-11_DC_1A-3A-7A-20A_n38A | ZTE Corporation |
| R4-2106646 | TP for TR 37.717-41-11: DC_1A-3A-7A-38A_n28A/DC_1A-3C-7A-38A_n28A | Huawei, HiSilicon |
| R4-2107067 | TP for TR 37 717-41-11 to include DC_1A-3A-7A-28A_n3A | Ericsson,Telstra |
| R4-2107068 | TP for TR 37 717-41-11 to include DC_2A-5A-30A-66A_n2A | Ericsson, AT&T |
| R4-2107069 | TP for TR 37 717-41-11 to include DC_2A-5A-30A-66A_n66A | Ericsson, AT&T |
| R4-2107070 | TP for TR 37 717-41-11 to include DC_2A-14A-30A-66A_n2A | Ericsson, AT&T |
| R4-2107071 | TP for TR 37 717-41-11 to include DC_2A-14A-30A-66A_n66A | Ericsson, AT&T |
| R4-2107072 | TP for TR 37 717-41-11 to include DC_2A-29A-30A-66A_n66A | Ericsson, AT&T |
| 7.6.3 | EN-DC with FR2 band | |
| R4-2107073 | TP for TR 37 717-41-11 to include DC_2A-29A-30A-66A_n260M | Ericsson, AT&T |
| 7.7.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2104965 | TR 37.717-11-21 v0.4.0 TR update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 | LG Electronics France |
| R4-2104966 | Revised WID on LTE (xDL/UL x=1.2,3,4) with NR 2 bands (2DL/1UL) DC in Rel-17 | LG Electronics France |
| 7.7.2 | EN-DC including NR inter CA without FR2 band | |
| R4-2104967 | TP on summary of self-interference analysis for new NR DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 | LG Electronics France |
| R4-2104968 | MSD anlaysis results for new DC band combinations | LG Electronics France |
| R4-2105272 | TP for TR 37.717-11-21 to include 2_n25-n66 | Ericsson, Bell Mobility |
| R4-2106378 | TP for TR 37.717-11-21: DC_1A-3A-20A_n7A-n78A | ZTE Corporation |
| R4-2106647 | TP for TR 37.717-11-21:DC_40A_n1A-n78A/DC_40C_n1A-n78A | Huawei, HiSilicon |
| R4-2106743 | TP for TR 37.717-11-21 to include 2_n25-n66 | Ericsson, Bell Mobility |
| R4-2106744 | TP for TR 37.717-11-21 to include 7_n25-n66 | Ericsson, Bell Mobility |
| R4-2106745 | TP for TR 37.717-11-21 to include 13_n25-n66 | Ericsson, Bell Mobility |
| R4-2106746 | TP for TR 37.717-11-21 to include 66_n25-n66 | Ericsson, Bell Mobility |
| R4-2106747 | TP for TR 37.717-11-21 to include DC_2-7_n25-n66 | Ericsson, Bell Mobility |
| R4-2106748 | TP for TR 37.717-11-21 to include DC_2-13_n25-n66 | Ericsson, Bell Mobility |
| R4-2106749 | TP for TR 37.717-11-21 to include 2-66_n25-n66 | Ericsson, Bell Mobility |
| R4-2106750 | TP for TR 37.717-11-21 to include 7-13_n25-n66 | Ericsson, Bell Mobility |
| R4-2106751 | TP for TR 37.717-11-21 to include 7-66_n25-n66 | Ericsson, Bell Mobility |
| R4-2106752 | TP for TR 37.717-11-21 to include 2-7-13_n25-n66 | Ericsson, Bell Mobility |
| R4-2106753 | TP for TR 37.717-11-21 to include 2-7-66_n25-n66 | Ericsson, Bell Mobility |
| R4-2106758 | TP for TR 37.717-11-21 to include 1-7-28_n3-n78 | Ericsson, Telstra |
| R4-2106763 | TP for TR 37.717-11-21 to include 3-7_n3-n78 | Ericsson, Telstra |
| R4-2106764 | TP for TR 37.717-11-21 to include 3-28_n3-n78 | Ericsson, Telstra |
| R4-2106765 | TP for TR 37.717-11-21 to include 1-3-7_n3-n78 | Ericsson, Telstra |
| R4-2106766 | TP for TR 37.717-11-21 to include 1-3-28_n3-n78 | Ericsson, Telstra |
| R4-2106767 | TP for TR 37.717-11-21 to include 3-7-28_n3-n78 | Ericsson, Telstra |
| R4-2106768 | TP for TR 37.717-11-21 to include 1-3-7-28_n3-n78 | Ericsson, Telstra |
| 7.7.3 | EN-DC including NR inter CA with FR2 band | |
| R4-2106755 | TP for TR 37.717-11-21 to include 28_n7-n258 | Ericsson, Telstra |
| 7.8.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106660 | TR 37.717-00-00 v0.4.0 | Huawei, HiSilicon |
| 7.8.2 | UE RF | |
| R4-2105008 | Draft CR on n97 for coexistence with protected bands | CMCC, Huawei, HiSilicon |
| R4-2105009 | TP to TR 37.717-00-00 for SUL_n41A-n97A | CMCC |
| R4-2105164 | TP for TR 37.717-00-00:SUL_n24A-n99A | Huawei,HiSilicon |
| R4-2105165 | TP for TR 37.717-00-00:SUL_n41A-n99A and SUL_n41A(2A)-n99A | Huawei,HiSilicon |
| R4-2105166 | TP for TR 37.717-00-00:SUL_n48A-n99A and SUL_n48A(2A)-n99A | Huawei,HiSilicon |
| R4-2105167 | TP for TR 37.717-00-00:SUL_n77A-n99A and SUL_n77A(2A)-n99A | Huawei,HiSilicon |
| R4-2105168 | Draft CR to 38.101-1 to modify supplementary uplink configuration for reference sensitivity | Huawei,HiSilicon |
| R4-2105273 | Draft CR on n97 for coexistence with protected bands | CMCC, Huawei, HiSilicon |
| R4-2105274 | TP to TR 37.717-00-00 for SUL_n41A-n97A | CMCC |
| R4-2105275 | TP for TR 37.717-00-00:SUL_n24A-n99A | Huawei,HiSilicon |
| R4-2105276 | TP for TR 37.717-00-00 for SUL_n41A-n97A | Huawei, HiSilicon |
| R4-2106654 | Updated TP for TR 37.717-00-00 for CA_n3A_SUL_n78C-n80A | Huawei, HiSilicon |
| R4-2106655 | Updated TP for TR 37.717-00-00 for CA_n1A_SUL_n78C-n84A | Huawei, HiSilicon |
| R4-2106656 | Updated TP for TR 37.717-00-00 for CA_n28A_SUL_n41C-n83A | Huawei, HiSilicon |
| R4-2106657 | Updated TP for TR 37.717-00-00 for CA_n28A_SUL_n79C-n83A | Huawei, HiSilicon |
| R4-2106658 | TP for TR 37.717-00-00 for SUL_n41A-n97A | Huawei, HiSilicon |
| 7.9.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2104807 | TR 38.717-03-01 on Rel-17 NR inter-band Carrier Aggregation (CA) for 3 Down Link (DL) / 1 Up Link (UL) | CATT |
| 7.9.2 | UE RF | |
| R4-2104424 | TP to TR 38.717-03-01: CA_n25-n48-n66 combinations | Nokia, T-Mobile USA |
| R4-2104643 | TP for TR 38.717-03-01: CA_n1-n3-n20 | VODAFONE Group Plc |
| R4-2104644 | TP for TR 38.717-03-01: CA_n1-n20-n78 | VODAFONE Group Plc |
| R4-2104645 | TP for TR 38.717-03-01: CA_n3-n20-n78 | VODAFONE Group Plc |
| R4-2104646 | TP for TR 38.717-03-01: CA_n8-n28-n78 | VODAFONE Group Plc |
| R4-2104809 | Supported channel bandwidth for CA_n39-n41-n79 | CATT, CMCC |
| R4-2104810 | Supported channel bandwidth for CA_n39-n41-n79 | CATT, CMCC |
| R4-2104912 | TP for TR 38.717-03-01: NR CA_n3-n28-n79 | SoftBank Corp. |
| R4-2104915 | TP for TR 38.717-03-01: NR CA_n3-n79-n257 | SoftBank Corp. |
| R4-2104916 | TP for TR 38.717-03-01: NR CA_n28-n79-n257 | SoftBank Corp. |
| R4-2104917 | TP update for TR 38.717-03-01: NR CA_n28-n77-n79 | SoftBank Corp. |
| R4-2105070 | TP for TR 38.717-03-01: CA_n7-n25-n77 | Samsung, TELUS, Bell mobility |
| R4-2105071 | TP for TR 38.717-03-01: CA_n7-n66-n77 | Samsung, TELUS, Bell mobility |
| R4-2105072 | TP for TR 38.717-03-01: CA_n25-n66-n77 | Samsung, TELUS, Bell mobility |
| R4-2106652 | TP for TR 38.717-03-01: CA_n1A-n3A-n7A | Huawei, HiSilicon |
| R4-2106718 | TP for 37.717-03-01 to include n2-n5-n66 | Ericsson, AT&T |
| R4-2106720 | TP for 37.717-03-01 to include n2-n5-n30 | Ericsson, AT&T |
| R4-2106729 | TP for 37.717-03-01 to include n13-n25-n77 | Ericsson, Bell Mobility |
| R4-2106731 | TP for 37.717-03-01 to include n13-n66-n77 | Ericsson, Bell Mobility |
| 7.10.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106698 | Revised WID 4 bands NR CA Rel-17 | Ericsson |
| R4-2106702 | CR 38.101-1 introduction completed band combinations NR Inter-band 4 bands CA | Ericsson |
| R4-2106703 | CR 38.101-3 introduction completed band combinations NR Inter-band 4 bands CA | Ericsson |
| R4-2106706 | TR 38.717-04-01 v0.4.0 Rel-17 NR Inter-band 4 bands CA | Ericsson |
| 7.10.2 | UE RF | |
| R4-2104420 | TP to TR 38.717-04-01: CA_n25-n41-n71-n77 | Nokia, T-Mobile USA |
| R4-2104421 | TP to TR 38.717-04-01: CA_n25-n66-n71-n77 | Nokia, T-Mobile USA |
| R4-2104422 | TP to TR 38.717-04-01: CA_n25-n41-n66-n77 | Nokia, T-Mobile USA |
| R4-2105073 | TP for TR 38.717-04-01: CA_n7-n25-n66-n77 | Samsung, TELUS, Bell mobility |
| R4-2105277 | TP to TR 38.717-04-01: CA_n25-n41-n66-n77 | Nokia, T-Mobile USA |
| R4-2105278 | TP for TR 38.717-04-01: CA_n1A-n8A-n78A-n79A/ CA_n1A-n8A-n78(2A)-n79A | Huawei, HiSilicon |
| R4-2106653 | TP for TR 38.717-04-01: CA_n1A-n8A-n78A-n79A/ CA_n1A-n8A-n78(2A)-n79A | Huawei, HiSilicon |
| 7.11.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2104914 | TR 38.717-03-02 v0.4.0 | ZTE Wistron Telecom AB |
| R4-2106837 | TP for TR38.717-03-02_Removal of the sub-clauses under clause 5.2 | ShenZhen Zhongxing Shitong |
| 7.11.2 | UE RF | |
| R4-2104709 | TP to TR 38.717-03-02 CA_n7-n66-n77 | Nokia, Nokia Shanghai Bell |
| R4-2104710 | draft CR CA_n25_n66_n77 to TS 38.101-1 | Nokia, Nokia Shanghai Bell |
| R4-2105279 | TP to TR 38.717-03-02 CA_n7-n66-n77 | Nokia, Nokia Shanghai Bell |
| R4-2105280 | DraftCR for 38.101-1 to add additional combinations for CA_n25-n66-n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2105281 | TP to TR 38.717-03-02 Addition of CA_n2A-n5A-n66A | Nokia, Verizon |
| R4-2106383 | TP for TR38.717-03-02_ CA_n8A-n39A-n41A | ZTE Corporation |
| R4-2106496 | TP for TR 38.717-03-02: CA_n25-n71-n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106497 | DraftCR for 38.101-1 to add additional combinations for CA_n25-n66-n78 | Huawei, HiSilicon, Bell Mobility, Telus |
| R4-2106719 | TP for 38.717-03-02 to include n2-n5-n66 | Ericsson, AT&T |
| R4-2106721 | TP for 38.717-03-02 to include CA_n2-n5-n30 | Ericsson, AT&T |
| R4-2106730 | TP for 38.717-03-02 to include n13-n25-n77 | Ericsson, Bell Mobility |
| R4-2106732 | TP for 38.717-03-02 to include n13-n66-n77 | Ericsson, Bell Mobility |
| R4-2106770 | TP for 38.717-03-02 to include n41-n66-n71 | Ericsson, T-Mobile US |
| R4-2106771 | TP for 38.717-03-02 to include n25-n41-n66 | Ericsson, T-Mobile US |
| R4-2107209 | TP to TR 38.717-03-02 Addition of CA_n2A-n5A-n66A | Nokia, Verizon |
| 7.12.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106384 | TR 37.717-33 v0.2.0 | ZTE Corporation |
| 7.12.2 | UE RF | |
| R4-2106381 | TP for TR 37.717-33_DC_39A_n41A-n258A | ZTE Corporation |
| 7.13.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106385 | TR 37.717-11-31_v0.3.0 | ZTE Corporation |
| 7.14.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2105103 | TR 38.717-04-02 update version 0.4.0 | Samsung |
| 7.14.2 | UE RF | |
| R4-2105074 | TP for TR 38.717-04-02: CA_n7-n25-n66-n77 | Samsung, TELUS, Bell mobility |
| R4-2106374 | Draft CR to TS38.101-3 Introduction of DC_1A-3A-7A-20A_n78(2A) | ZTE Corporation |
| 7.15.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2106661 | TR 38.717-05-01 v0.2.0 | Huawei, HiSilicon |
| 7.15.2 | UE RF | |
| R4-2106769 | TP for 37.717-05-01 to include n1-n3-n7-n28-n78 | Ericsson, Telstra |
| 7.16.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2105091 | TR 37.717-51-11 update version 0.2.0 | Samsung |
| 7.17.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2105092 | TR 37.717-21-22 update version 0.2.0 | Samsung |
| 7.18 | Issues arising from basket WIs but not subject to block approval | |
| R4-2105179 | Draft Email Round 1discussion summary for [98-bis-e][106] NR_Baskets_Part_3 | Moderator (Skyworks Solutions Inc.) |
| R4-2105334 | Way forward on combinations not for block approval and their handling | Apple |
| R4-2105335 | Way forward on analysis and framework of triple beat issue of 3CC UL with contiguous intra band UL CA | Qualcomm Incorporated |
| R4-2105336 | Way forward on analysis and framework of IMD issue of 2CC contiguous and non-contiguous intra band UL CA | Skyworks |
| R4-2105337 | Way forward on analysis and framework of LB-LB-LB combinations | MediaTek, Vodafone |
| R4-2105338 | Way forward on single UL intra-band ENDC REFSENS Exceptions | Skyworks |
| R4-2105339 | Way forward on 2CC contiguous intra-band NRU UL CA | Qualcomm Incorporated |
| R4-2105443 | Email discussion summary for [98-bis-e][106] NR_Baskets_Part_3 | Moderator (Skyworks) |
| 7.18.1 | UE RF | |
| R4-2104650 | On support of DC_8-20_n1, DC_8-20_n3 and DC_8-20_n28 | VODAFONE Group Plc |
| R4-2104818 | Handling of Inter-band UL Configuration Including NR Intra-band ULCA | Skyworks Solutions Inc. |
| R4-2104820 | Draft CR for Pcmax - NR-DC for DC cat. A-B combinations | InterDigital Communications, Charter Communication Inc. |
| R4-2105340 | Draft CR for Pcmax - NR-DC for DC cat. A-B combinations | InterDigital Communications, Charter Communication Inc. |
| R4-2106908 | FR1 CA/DC band combinations not for block approval | Apple |
| R4-2107345 | Inter-band ULCA with more than 2CCs | Qualcomm Incorporated |
| 7.19 | SAR schemes for UE power class 2 (PC2) for NR inter-band Carrier Aggregation and supplemental uplink (SUL) configurations with 2 bands UL | |
| R4-2105341 | Way forward on SAR solutions for PC2 NR inter-band CA and SUL configurations | China Telecom |
| R4-2105342 | Way forward on increasing UE maximum power high limit | Qualcomm |
| R4-2105444 | Email discussion summary for [98-bis-e][107] NR_SAR_PC2_interB_SUL_2BUL_NWM | Moderator (China Telecom) |
| 7.19.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2105180 | Email discussion summary for [98-bis-e][107] NR_SAR_PC2_interB_SUL_2BUL | Moderator (China Telecom) |
| 7.19.2 | PC2 for inter-band CA | |
| R4-2104527 | Discussion on PC2 inter-band NR CA | vivo |
| R4-2105085 | More on methods for faciliating SAR compliance for inter-band UL CA | Ericsson |
| R4-2106275 | Further discussion on SAR schemes for UE power class 2 NR inter-band CA with 2UL | China Telecom |
| R4-2106363 | Further discussion on SAR solution for NR PC2 inter-band CA | ZTE Corporation |
| R4-2106541 | Discussion on SAR issue for HP UE inter-band UL CA | Xiaomi |
| R4-2106559 | R17 Inter band CA HPUE | OPPO |
| R4-2106905 | Power class consideration for NR inter-band UL CA | Apple |
| 7.19.3 | PC2 for SUL | |
| R4-2106276 | Further discussion on SAR schemes for UE power class 2 NR SUL configurations | China Telecom |
| 7.19.4 | Others | |
| R4-2104572 | Exploiting full potential of UE Tx power | Nokia Japan |
| R4-2105086 | Higher BC power class for UL CA | Ericsson |
| R4-2106557 | R17 Discussion on UE power class high limit | OPPO |
| 7.20 | High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink | |
| R4-2105445 | Email discussion summary for [98-bis-e][108] NR_PC2_CA_R17_2BDL_2BUL | Moderator (China Telecom |
| 7.20.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2105181 | Email discussion summary for [98-bis-e][108] NR_PC2_CA_R17_2BDL_2BUL | Moderator (China Telecom) |
| R4-2106277 | Draft TR 38.841 v0.3.0: High power UE for NR inter-band Carrier Aggregation with 2 bands downlink and x bands uplink (x =1,2) | China Telecom |
| R4-2106278 | Draft CR to 38.101-1 Introduce RF requirements for HPUE CA with 2 bands downlink and x bands uplink (x =1,2) | China Telecom |
| 7.20.2 | UE RF | |
| R4-2104973 | MSD results by self interference for PC2 high power NR inter-band CA UE | LG Electronics France |
| R4-2105343 | TP to 38.841: RF requirements for PC2 CA_n3A-n78A with up to 2 uplink | China Telecom |
| R4-2105344 | TP for TR_38.841 PC2 CA_n25A-n41A | T-Mobile USA |
| R4-2105345 | TP for TR_38.841 PC2 CA_n41A-n66A | T-Mobile USA |
| R4-2105346 | TP for TR_38.841 PC2 CA_n41A-n71A | T-Mobile USA |
| R4-2106279 | TP to 38.841: RF requirements for PC2 CA_n3A-n78A with up to 2 uplink | China Telecom |
| R4-2106561 | R17 MSD improvement | OPPO |
| R4-2106904 | Draft CR for TS 38.101-1: Inter-band UL CA power class correction | Apple |
| R4-2107315 | On power class for NR band in PC2 inter-band CA | Huawei, HiSilicon |
| R4-2107333 | TP for TR_38.841 PC2 CA_n25A-n41A | T-Mobile USA |
| R4-2107334 | TP for TR_38.841 PC2 CA_n41A-n66A | T-Mobile USA |
| R4-2107335 | TP for TR_38.841 PC2 CA_n41A-n71A | T-Mobile USA |
| 7.21 | High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band | |
| R4-2105182 | Email discussion summary for [98-bis-e][109] ENDC_UE_PC2_R17_NR_TDD | Moderator (China Unicom) |
| R4-2105446 | Email discussion summary for [98-bis-e][109] ENDC_UE_PC2_R17_NR_TDD | Moderator (China Unicom) |
| 7.21.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2104950 | Proposal on revision of WID table | China Unicom |
| R4-2106288 | TR 37.826 v0.3.0 ENDC_UE_PC2_R17_NR_TDD | China Unicom |
| 7.21.2 | UE RF | |
| R4-2104974 | MSD results by cross-band isolation for PC2 high power NR DC UE | LG Electronics France |
| R4-2104990 | TP for TR 37.826 on PC2 DC_5A_n78A | SK Telecom |
| R4-2104993 | TP for TR 37.826 on PC2 DC_7A_n78A | SK Telecom |
| R4-2105347 | TP for TR 37.826 on PC2 DC_5A_n78A | SK Telecom |
| R4-2105348 | TP for TR 37.826 on PC2 DC_7A_n78A | SK Telecom |
| R4-2105349 | TP for TR 37.826 PC2 DC_2A_n41A | T-Mobile USA |
| R4-2107331 | TP for TR 37.826 PC2 DC_2A_n41A | T-Mobile USA |
| R4-2107332 | TP for TR 37.826 PC2 DC_66A_n41A | T-Mobile USA |
| 7.22 | Power Class 2 UE for NR inter-band CA and SUL configurations with x (x>2) bands DL and y (y=1, 2) bands UL | |
| R4-2105447 | Email discussion summary for [98-bis-e][110] NR_UE_PC2_CA_SUL_xBDL_yBUL | Moderator (Huawei) |
| 7.22.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2107276 | Draft TR 38.xxx High power UE (power class 2) for NR inter-band CA and SUL with x (x>2) bands DL and y (y=1, 2) bands UL | Huawei, HiSilicon |
| 7.22.2 | UE RF | |
| R4-2105183 | Email discussion summary for [98-bis-e][110] NR_UE_PC2_R17_CA_SUL_xDL_yUL | Huawei |
| R4-2105350 | Considerations on high order band combinations for PC2 inter-band CA and SUL | Huawei, HiSilicon |
| R4-2107268 | Considerations on high order band combinations for PC2 inter-band CA and SUL | Huawei, HiSilicon |
| 7.23 | Power Class 2 for EN-DC with xLTE band + yNR DL with 1LTE+1(TDD) NR UL band (x= 2, 3, 4, y=1; x=1, 2, y=2) | |
| R4-2105184 | Email discussion summary for [98-bis-e][111] ENDC_PC2_R17_xLTE_yNR | Moderator (Ericsson) |
| R4-2105359 | Email discussion summary for [98-bis-e][111] ENDC_PC2_R17_xLTE_yNR | Moderator (Ericsson) |
| R4-2105448 | (Email discussion summary for [98-bis-e][111] ENDC_PC2_R17_xLTE_yNR | Moderator (Ericsson) |
| 7.23.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2105489 | TR 37.827 v0.0.1 ENDC_PC2_R17_xLTE_yNR | Ericsson |
| 7.23.2 | UE RF | |
| R4-2104498 | TP for TR 37.xxx for DC_2-5_n77 | Verizon Denmark |
| R4-2104499 | TP for TR 37.xxx for DC_2-13_n77 | Verizon Denmark |
| R4-2104500 | TP for TR 37.xxx for DC_2-66_n77 | Verizon Denmark |
| R4-2104501 | TP for TR 37.xxx for DC_5-66_n77 | Verizon Denmark |
| R4-2104502 | TP for TR 37.xxx for DC_13-66_n77 | Verizon Denmark |
| R4-2104503 | TP for TR 37.xxx for DC_2_n5-n77 | Verizon Denmark |
| R4-2104504 | TP for TR 37.xxx for DC_66_n2-n77 | Verizon Denmark |
| R4-2104505 | TP for TR 37.xxx for DC_66_n5-n77 | Verizon Denmark |
| R4-2105351 | TP for TR 37.xxx for DC_2-5_n77 | Verizon Denmark |
| R4-2105352 | TP for TR 37.xxx for DC_2-13_n77 | Verizon Denmark |
| R4-2105353 | TP for TR 37.xxx for DC_2-66_n77 | Verizon Denmark |
| R4-2105354 | TP for TR 37.xxx for DC_5-66_n77 | Verizon Denmark |
| R4-2105355 | TP for TR 37.xxx for DC_13-66_n77 | Verizon Denmark |
| R4-2105356 | TP for TR 37.xxx for DC_2_n5-n77 | Verizon Denmark |
| R4-2105357 | TP for TR 37.xxx for DC_66_n2-n77 | Verizon Denmark |
| R4-2105358 | TP for TR 37.xxx for DC_66_n5-n77 | Verizon Denmark |
| R4-2107049 | Discussion on the support of PC2 FDD-TDD EN-DC with more aggregated bands on the downlink | CHTTL |
| 7.24 | Adding channel bandwidth support to existing NR bands | |
| R4-2105185 | Email discussion summary for [98-bis-e][112] NR_bands_R17_BWs | Moderator (Ericsson) |
| R4-2105360 | Way forward on adding 90 and 100MHz channel BW for UE in band n40 | Huawei |
| R4-2105361 | Way forward on the introduction of 25, 30 and 40MHz in band n2 | AT&T |
| R4-2105362 | Way forward on the introduction of 25MHz in band n5 | AT&T |
| R4-2105363 | Way forward on the introduction 50MHz in band n3 | Ericsson, China Telecom, China Unicom |
| R4-2105449 | Email discussion summary for [98-bis-e][112] NR_bands_R17_BWs | Moderator (Ericsson) |
| R4-2105493 | Email discussion summary for [98-bis-e][112] NR_bands_R17_BWs | Moderator (Ericsson) |
| 7.24.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2106285 | Draft CR to 38.101-1 Introduce 50MHz CBW for Band n3 | China Telecom |
| R4-2106286 | Draft CR to 38.104 Introduce 50MHz CBW for Band n3 | China Telecom |
| R4-2106892 | Revised Basket WID on adding channel bandwidth support to existing NR bands | Ericsson |
| R4-2106893 | Basket WID on new CBW - update | Ericsson |
| 7.24.2 | UE RF requirement | |
| R4-2105323 | n5 25MHz | Qualcomm Incorporated |
| R4-2106480 | Adding 90 and 100MHz bandwidth for band n40 | Huawei, HiSilicon, CMCC |
| R4-2106482 | Adding 50 MHz CBW for NR band n3 | Huawei, HiSilicon |
| R4-2107320 | n5 25MHz | Qualcomm Incorporated |
| R4-2107321 | n3 50MHz | Qualcomm Incorporated |
| R4-2107323 | n5 25MHz REFSENS A-MPR | Skyworks Solutions Inc. |
| 7.24.2.1 | Reference sensitivity | |
| R4-2104657 | REFSENS of n5 for 25MHz channel bandwidth | Murata Manufacturing Co Ltd. |
| R4-2104658 | REFSENS of n2 for 30MHz and 40MHz channel bandwidth | Murata Manufacturing Co Ltd. |
| R4-2104890 | MSD calculation for band n5 with 20 MHz UL BW | Apple |
| R4-2104959 | n5 REFSENS supporting 25MHz CBW | MediaTek Inc. |
| R4-2105006 | MSD due to cross band isolation evaluation for n40 supporting 90/100MHz CBW | MediaTek Inc. |
| R4-2106284 | Discussion on RefSens for Band n3 50MHz CBW | China Telecom |
| R4-2107325 | n2 25,30,40MHz REFSENS | Skyworks Solutions Inc. |
| 7.24.2.2 | MPR/A-MPR/NS signaling | |
| R4-2104880 | Discussion on new CBW 90MHz and 100MHz for n40 | Apple |
| R4-2104881 | Discussion and proposal for n5 with 25MHz CBW | Apple |
| R4-2107324 | n40 90M 100M BWs | Qualcomm Incorporated |
| 7.24.3 | BS RF requirement | |
| R4-2106481 | draftCR to 38104: adding 90MHz BW for band n40 | Huawei, HiSilicon, CMCC |
| R4-2106906 | FR1 REFSENS table split and simplification | Apple |
| 7.25 | Introduction of channel bandwidths 35MHz and 45MHz for NR | |
| R4-2105186 | Email discussion summary for [98-bis-e][113] NR_FR1_35MHz_45MHz_BW | Moderator (Huawei) |
| R4-2105364 | Way forward on UE REFSENS for 35 MHz and 45 MHz | Huawei |
| R4-2105365 | Way forward on REFSENS table split and simplification | Apple |
| R4-2105366 | Way forward on A-MPR for n1 45 MHz | China Telecom |
| R4-2105450 | Email discussion summary for [98-bis-e][113] NR_FR1_35MHz_45MHz_BW | Moderator (Huawei) |
| 7.25.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2106283 | Draft CR to 38.101-1 Introduce band specific requirements for 45MHz CBW for Band n1 | China Telecom |
| 7.25.3 | UE RF requirements | |
| R4-2104656 | REFSENS of n8, n71, n25 for 35_45MHz channel bandwidth | Murata Manufacturing Co Ltd. |
| R4-2104811 | REFSENS evaluation of n8 and n71 for 35MHz channel bandwidth | Mediatek India Technology Pvt. |
| R4-2104878 | n1 35 and 45MHz BW AMPR | Qualcomm Technologies Int |
| R4-2104888 | UL channel location for MSD calculation for bands n8 and n71 | Apple |
| R4-2105171 | n1 35 and 45MHz BW AMPR | Qualcomm |
| R4-2106282 | Discussion on A-MPR for 45MHz CBW for Band n1 | China Telecom |
| R4-2106483 | UE REFSENS for 35 MHz and 45 MHz | Huawei, HiSilicon |
| R4-2106484 | A-MPR for n1 45MHz | Huawei, HiSilicon |
| R4-2107337 | 35-45MHz REFSENS for n2 n3 n8 n25 n71 | Skyworks Solutions Inc. |
| R4-2107339 | 35MHz and 45MHz REFSENS | Qualcomm Incorporated |
| 7.25.5 | RRM requirements | |
| R4-2104602 | Discussion on impact of 35MHz and 45MHz introduction on RRM test cases | CMCC |
| R4-2105684 | Email discussion summary for [98-bis-e][214] Spectrum_RRM | Moderator (Ericsson) |
| R4-2105784 | WF on RRM requirements for spectrum WIs | Ericsson |
| R4-2105816 | Email discussion summary for [98-bis-e][214] Spectrum_RRM | Moderator (Ericsson) |
| R4-2106940 | Discussion on RRM impact on channel bandwidths 35MHz and 45MHz for NR FR1 | Huawei, HiSilicon |
| R4-2107156 | Impact of new FR1 channel BWs on RRM requirements | Ericsson |
| 7.25.6 | UE Demod | |
| R4-2104601 | Discussion on impact of 35MHz and 45MHz introduction on demodulation test cases | CMCC |
| R4-2105991 | Email discussion summary for [98-bis-e][320] NR_R17_SpectrumWI_Demod_NWM | Moderator (Ericsson) |
| R4-2106090 | Way forward on UE demodulation and CQI reporting for channel bandwidths 35MHz and 45MHz for NR FR1 | Ericsson |
| R4-2106142 | Email discussion summary for [98-bis-e][320] NR_R17_SpectrumWI_Demod_NWM | Moderator (Ericsson) |
| R4-2106832 | Discussion on NR UE demodulation for 35MHz and 45MHz bandwidth | Huawei, HiSilicon |
| R4-2106872 | UE demodulation requirements for CBW 35MHz/45MHz | Ericsson |
| 7.26 | Band combinations for Uu and V2X con-current operation | |
| R4-2105187 | Email discussion summary for [98-bis-e][114] NR_LTE_V2X_PC5_combos | Moderator (CATT) |
| R4-2105451 | Email discussion summary for [98-bis-e][114] NR_LTE_V2X_PC5_combos | Moderator (CATT) |
| 7.26.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2104770 | Draft CR for TS 38.101-1, Introduce new band combination of V2X_n79A-n47A | CATT |
| R4-2104771 | Draft CR for TS 38.101-3, Introduce new band combination of V2X_n79A-47A | CATT |
| R4-2104772 | TR 37.875, Band combinations for V2X con-current operation | CATT |
| R4-2105367 | Draft CR for TS 38.101-1, Introduce new band combination of V2X_n79A-n47A | CATT |
| R4-2105368 | Draft CR for TS 38.101-3, Introduce new band combination of V2X_n79A-47A | MCATT |
| R4-2105369 | Scope of NR V2X R17 combinations | Huawei, HiSilicon |
| R4-2107297 | Scope of NR V2X R17 combinations | Huawei, HiSilicon |
| 7.26.2 | UE RF requirement for concurrent operation between NR Uu band and NR PC5 band | |
| R4-2104769 | TP on V2X_n79A-n47A and V2X_n79A-47A coexistence study | CATT |
| 7.27.1 | UE RF (38.101-2) | |
| R4-2104492 | Power class specific parameters for n262 | Qualcomm Incorporated |
| R4-2105188 | Email discussion summary for [98-bis-e][115] NR_47GHz_Band | Hisashi Onozawa (Nokia) |
| R4-2105370 | Way forward on n262 UE RF | Nokia |
| R4-2105452 | Email discussion summary for [98-bis-e][115] NR_47GHz_Band | Moderator (Nokia) |
| 7.27.1.1 | Peak EIRP and EIRP spherical coverage | |
| R4-2104516 | Discussion on EIRP for PC1,PC2 and PC4 | vivo |
| R4-2104695 | Peak EIRP and EIRP spherical coverage for PC1, PC2, PC4 for n262 | Sony, Ericsson |
| R4-2104712 | EIRP requirements for n262 UE power class 1, 2, and 4 | Nokia, Nokia Shanghai Bell |
| 7.27.1.2 | Other UE TX requirements | |
| R4-2104713 | Introduction of n262 UE RF requirements | Nokia, Nokia Shanghai Bell |
| R4-2104889 | Beam correspondence side conditions for SSB and CSI-RS in band n262 | Apple |
| 7.27.1.3 | REFSENS and EIS spherical coverage | |
| R4-2104517 | Discussion on EIS for PC1,PC2 and PC4 | vivo |
| R4-2104696 | REFSENS and EIS spherical coverage for PC1, PC2, PC4 for n262 | Sony, Ericsson |
| R4-2104714 | EIS requirements for n262 UE power class 1, 2, and 4 | Nokia, Nokia Shanghai Bell |
| 7.27.3 | RRM (38.133) | |
| R4-2105858 | Draft Big CR: RRM requirements for band n262 in 38.133 | Ericsson |
| R4-2107147 | Analysis of RRM core requirements for band n262 | Ericsson |
| R4-2107148 | RRM core requirements for band n262 in 38.133 | Ericsson |
| 7.27.4.1 | BS conformance (38.141) | |
| R4-2105977 | Email discussion summary for [98-bis-e][306] NR_47GHz_Band_BSRF_NWM | Moderator (Nokia) |
| R4-2106143 | Email discussion summary for [98-bis-e][306] NR_47GHz_Band_BSRF_NWM | Moderator (Nokia) |
| R4-2106890 | 47GHz band - Measurement uncertainties for BS requirements | Ericsson |
| R4-2107038 | TP to TR 38.847: BS conformance aspects | Nokia, Nokia Shanghai Bell |
| R4-2107039 | Draft CR to 38.141-2: Introduction of n262 | Nokia, Nokia Shanghai Bell |
| R4-2107077 | 47 GHz band TT for NR BS RF requirement | Keysight Technologies UK Ltd |
| 7.27.4.2 | UE Demod (38.101-4) | |
| R4-2104843 | On UE Demodulation requirements for band n262 | Apple |
| R4-2106091 | Way forward on UE/BS demodulation on NR 47GHz band | Ericsson |
| R4-2106468 | Discussion on PDSCH Demodulation Requirements for 47 GHz band | Qualcomm Incorporated |
| R4-2106823 | Discussion on NR UE demodulation for 47GHz band | Huawei, HiSilicon |
| R4-2106859 | Applicability of FR2 UE demodulation requirements for NR 47GHz band | Ericsson |
| R4-2106860 | pCR to 38.847: UE performance requirements | Ericsson |
| R4-2106861 | draft CR: TS 38.101-4: n262 demodulation requirements | Ericsson |
| 7.27.4.3 | BS Demod (38.104) | |
| R4-2104682 | pCR to TR 38.847: BS demodulation requirements | Ericsson |
| R4-2106781 | On 47GHz OTA demodulation testing | Nokia, Nokia Shanghai Bell |
| R4-2106824 | Discussion on NR BS demodulation for 47GHz band | Huawei, HiSilicon |
| 7.27.4.4 | Others | |
| R4-2106889 | TR 38.847 Introduction of NR Band n262 (47GHz band) | Ericsson |
| R4-2107149 | Analysis of RRM performance requirements for band n262 | Ericsson |
| R4-2107150 | RRM performance requirements for band n262 in 38.133 | Ericsson |
| 7.28 | Introduction of NR band n24 | |
| R4-2105189 | Email discussion summary for [98-bis-e][116] NR_LTE_band_n24 | Moderator (Ligado Network) |
| R4-2105371 | Way forward on n24 emissions and A-MPR | Ligado Networks |
| R4-2105453 | Email discussion summary for [98-bis-e][116] NR_LTE_band_n24 | Moderator (Ligado Networks) |
| 7.28.1 | UE RF (38.101-1) | |
| R4-2107356 | A-MPR for Band n24 | Qualcomm Incorporated |
| 7.29 | Introduction of NR band n67 | |
| R4-2105372 | Way forward on band n85 | Ercisson |
| R4-2105454 | Email discussion summary for [98-bis-e][117] NR_n67_n85_NWM | Moderator (Ericsson |
| 7.29.3 | RRM (38.133) | |
| R4-2107118 | Further discussion on candidate methods for BCS4 | Qualcomm Incorporated |
| 7.29.4 | Others | |
| R4-2106894 | New NR band n67 - update | Ericsson |
| 7.30.1 | UE RF (38.101-1) | |
| R4-2105190 | [98-bis-e][117] NR_n67_n85_NWM | Moderator (Ericsson) |
| R4-2106896 | New NR band n85 - UE RF additional impacts | Ericsson |
| 7.30.2 | BS RF (38.104) | |
| R4-2106895 | New NR band n85 - BS RF additional impacts | Ericsson |
| 7.31 | Introduction of bandwidth combination set 4 (BCS4) for NR | |
| R4-2105191 | Email discussion summary for [98-bis-e][118] NR_BCS4 | Moderator (Ericsson) |
| R4-2105373 | Way forward on Possible improvements on MSD in relation to BCS4 | Huawei |
| R4-2105455 | Email discussion summary for [98-bis-e][118] NR_BCS4 | Moderator (Ericsson |
| R4-2105490 | Way forward on open issues for BCS4 (other than MSD) | T-Mobile USA |
| 7.31.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2105007 | BCS4 discussion | MediaTek Inc. |
| R4-2106367 | Templates for BCS4 configurations for inter-band NR CA | ZTE Corporation |
| R4-2106679 | General discussion on introduction of BCS4 | Huawei, HiSilicon |
| 7.31.2 | UE RF requirements | |
| R4-2107327 | BCS4 Progress | T-Mobile USA |
| 7.31.2.1 | MSD | |
| R4-2106677 | Discussion on how to simplify MSD definition using bandwidth-agnostic approach | Huawei, HiSilicon |
| R4-2107322 | Impact of Large NR BW on Crossband MSD | Skyworks Solutions Inc. |
| R4-2107346 | Urgency of new BCSs in the BCS4 WID | T-Mobile USA Inc. |
| 7.31.2.2 | Others (in case MPR/A-MPR is needed) | |
| R4-2106678 | Discussion on MSD due to cross band isolation and counter intermodulations | Huawei, HiSilicon |
| 7.31.3 | Signalling | |
| R4-2105093 | The signalling for BCS4 | Xiaomi |
| R4-2106680 | Discussion on UE capability for BCS4 | Huawei, HiSilicon |
| 7.32 | High power UE for NR TDD intra-band carrier aggregation in frequency range FR1 | |
| R4-2105192 | Email discussion summary for [98-bis-e][119]NR_intra_HPUE_UL_MIMO_bands | Moderator (Huawei, HiSilicon) |
| R4-2105374 | Way forward on PC2 UL MIMO for Band n40 | Huawei, HiSilicon |
| R4-2105456 | Email discussion summary for [98-bis-e][119] NR_intra_HPUE_UL_MIMO_bands | Moderator (Huawei) |
| 7.32.2.3 | others | |
| R4-2107344 | HPUE MPR with 1PA architecture | Qualcomm Incorporated |
| 7.33.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2107314 | draftCR for TS 38.101-1: introduce UL MIMO configurations for band n40 | Huawei, HiSilicon |
| 7.34 | Downlink interruption for band combinations to conduct dynamic Tx Switching | |
| R4-2105375 | TP on update the note of DL interruption applicability for 37.867 | CMCC |
| R4-2105376 | TP on DL interruption applicability of CA_n3-n40 for 37.867 | CMCC |
| R4-2105457 | Email discussion summary for [98-bis-e][120] DL_intrpt_combos_TxSW_R17 | Moderator (China Telecom) |
| 7.34.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2104801 | TR 37.867 v0.2.0 | CATT |
| R4-2105193 | Email discussion summary for [98-bis-e][120] DL_intrpt_combos_TxSW_R17 | Moderator (China Telecom) |
| R4-2106280 | Draft CR to 38.101-1 Introduce DL interruption clarification for CA conduting Tx Switching | China Telecom |
| 7.34.2 | Determination of inter-band uplink CA and EN-DC combinations for which DL interruption is not allowed | |
| R4-2104589 | TP on update the note of DL interruption applicability for 37.867 | CMCC |
| R4-2104590 | TP on DL interruption applicability of CA_n3-n40 for 37.867 | CMCC |
| R4-2106281 | TP to 37.867: DL interruption clarification for CA_n1-n3-n78 | China Telecom |
| 7.34.3 | Others | |
| R4-2104591 | DL interruption applicability of dynamic Tx switching for different cases | CMCC |
| 7.35 | Simultaneous Rx/Tx band combinations for CA, SUL, MR-DC and NR-DC | |
| R4-2105194 | Email discussion summary for [98-bis-e][121] Simultaneous_RxTx | Moderator (Huawei, HiSilicon) |
| R4-2105377 | Way forward on Simultaneous Rx/Tx | Huawei, HiSilicon |
| R4-2105458 | Email discussion summary for [98-bis-e][121] Simultaneous_RxTx | Moderator (Huawei) |
| 7.35.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2107311 | TR skeleton for simultaneous Rx/Tx band combinations | Huawei, HiSilicon |
| 7.35.2 | Criteria and analysis of Sim. RX/TX | |
| R4-2106386 | Discussion on Simultaneous RxTx | ShenZhen Zhongxing Shitong |
| R4-2106553 | R17 Discussion on simultaneous TxRx | OPPO |
| R4-2107047 | Discussion on general principle for simultaneous Rx/Tx band combinations for CA, SUL, MR-DC and NR-DC | CHTTL |
| R4-2107310 | On principles for deciding simultaneous Rx/Tx capability | Huawei, HiSilicon |
| 7.36 | Support of full bandwidth combinations for inter-band EN-DC | |
| R4-2105195 | Email discussion summary for [98bis-e] [122] Full_BW_Inter_band_ENDC | Moderator (Huawei) |
| R4-2105378 | Way forward on how to handle the MSD requirements for inter-band ENDC | Huawei, HiSilicon |
| R4-2105379 | Draft CR for 38.101-3 to introduce the missing MSD requirements (Rel-16) | Huawei, HiSilicon |
| R4-2105459 | Email discussion summary for [98-bis-e][122] Full_BW_Inter_Band_ENDC | Moderator (Huawei) |
| 7.36.1 | General and Rapporteur Input (WID/TR/CR) | |
| R4-2106681 | General discussion on support of full bandwidth combinations for inter-band EN-DC | Huawei, HiSilicon |
| 7.36.2 | UE RF requirements | |
| R4-2106682 | Draft CR for 38.101-3 to introduce the missing MSD requirements (Rel-16) | Huawei, HiSilicon |
| 7.37 | High-power UE operation for use cases in Band n77 and n78 | |
| R4-2105196 | Email discussion summary for [98-bis-e][123]HPUE_PC1_5_n77_n78 | Moderator (Qualcomm Incorporated) |
| R4-2105380 | Way forward on MPR for PC 1.5 | T-Mobile USA |
| R4-2105381 | Way forward on UE RF requirements for PC 1.5 in Band n79 | CMCC |
| R4-2105382 | Way forward on RF exposure mitigation approaches for PC 1.5 | Samsung |
| R4-2105460 | Email discussion summary for [98-bis-e][123] HPUE_PC1_5_n77_n78 | Moderator (Qualcomm) |
| R4-2105492 | Way forward on MPR for PC 1.5 | T-Mobile USA |
| 7.37.2 | PC1.5 UE RF requirements | |
| R4-2104975 | MPR for PC 1.5 NR UE on n77/n78 or n79 | LG Electronics France |
| 7.37.2.1 | A-MPR | |
| R4-2107317 | Discussion on PC1.5 performance for FWA | Skyworks Solutions Inc. |
| R4-2107352 | PC 1.5 for FWA devices | Qualcomm Incorporated |
| 7.37.2.2 | others | |
| R4-2105035 | MPE handling for high power FWA devices | Samsung |
| R4-2107264 | On the RF exposure limit for FWA PC1.5 | Huawei, HiSilicon |
| 7.38 | Introduction of lower 6GHz NR unlicensed operation for Europe | |
| R4-2105197 | Email discussion summary for [98-bis-e][124] NR_6GHz_unlic_EU | Moderator (Nokia) |
| R4-2105383 | Way forward on introduction of lower 6GHz NR unlicensed operation for Europe | Nokia |
| R4-2105384 | TP to TR 38.849 on NR-ARFCN and GSCN points | Nokia |
| R4-2105461 | Email discussion summary for [98-bis-e][124] NR_6GHz_unlic_EU | Moderator (Nokia) |
| 7.38.1 | General | |
| R4-2104882 | Band plan for lower 6GHz NR unlicensed operation for Europe | Apple |
| R4-2106273 | RF front-end supporting NRU in 6GHz EU spectrum with band n96 | Skyworks Solutions Inc. |
| R4-2107196 | draft TR 38.849 v0.2.0 | Nokia, Nokia Shanghai Bell |
| R4-2107197 | On system parameters for the lower 6GHz NR unlicensed operation | Nokia, Nokia Shanghai Bell |
| 7.38.2 | UE RF requirements | |
| R4-2106274 | A-MPR due to in-band PSD limit for 6GHz EU unlicensed spectrum | Skyworks Solutions Inc. |
| R4-2107198 | On UE RF aspects for the lower 6GHz NR unlicensed operation | Nokia, Nokia Shanghai Bell |
| R4-2107351 | A-MPR for European NR-U 6 GHz band | Qualcomm Incorporated |
| 7.38.3 | BS RF requirements | |
| R4-2106604 | Discussion on BS RF requirements for Europe unlicensed 6GHz | ZTE Corporation |
| R4-2106659 | draft CR for introduction of Europe unlicensed 6GHz | ZTE Corporation |
| R4-2107199 | On BS RF aspects for the lower 6GHz NR unlicensed operation | Nokia, Nokia Shanghai Bell |
| 7.38.4 | Others | |
| R4-2104883 | On simultaneous low power and very low power operation | Apple |
| 7.39 | Introduction of FR2 FWA UE with maximum TRP of 23dBm for band n259 | |
| R4-2105385 | Way forward on PC5 requirements in n259 | Qualcomm |
| R4-2105462 | Email discussion summary for [98-bis-e][125] NR_FR2_FWA_Bn259 | Moderator (Qualcomm) |
| 7.39.1 | UE RF | |
| R4-2104493 | PC5 RF requirements in n259 | Qualcomm Incorporated |
| R4-2104697 | Views on RF requirement for FWA | Sony, Ericsson |
| R4-2105198 | Email discussion summary for [98-bis-e][125] NR_FR2_FWA_Bn259 | Moderator (Qualcomm Incorporated) |
| R4-2106556 | R17 n259 FWA | OPPO |
| R4-2107341 | PC5 RF requirements for band n259 | Intel Corporation |
| 7.39.2 | RRM Perf. requirements | |
| R4-2107157 | Impact of FR2 FWA for band n259 on RRM requirements | Ericsson |
| 7.40.1 | General | |
| R4-2104893 | Considerations for PC1.5 with band n79 | Apple |
| R4-2105010 | Draft CR on PC1.5 HPUE SAR issue into Rel-16 TS 38.101-1 | CMCC |
| R4-2105011 | Draft CR on PC1.5 HPUE SAR issue into Rel-17 TS 38.101-1 | CMCC |
| 7.40.2 | PC1.5 UE RF requirements | |
| R4-2104957 | Discussion on PC1.5 with n79 | vivo |
| R4-2105012 | Discussion on the PC1.5 UE RF requirements of NR n79 | CMCC |
| R4-2105013 | Draft CR on PC1.5 UE RF requirements of n79 in Rel-17 TS 38.101-1 | CMCC |
| 7.40.2.1 | A-MPR | |
| R4-2107353 | PC 1.5 in Band n79 | Qualcomm Incorporated |
| 7.41 | High power UE (power class 2) for NR band n34 | |
| R4-2105199 | Email discussion summary for [98-bis-e][126] HPUE_n34_n39 | Moderator (CMCC) |
| R4-2105386 | Way forward on PC2 n34 and n39 for NR | CMCC |
| R4-2105463 | Email discussion summary for [98-bis-e][126] HPUE_n79_n34_n39 | Moderator (CMCC) |
| 7.41.2 | UE RF requirements | |
| R4-2105014 | Discussion on the PC2 UE RF requirements of NR n34 | CMCC |
| R4-2105015 | Draft CR on PC2 UE RF requirements of n34 in Rel-17 TS 38.101-1 | CMCC |
| R4-2106548 | Discussion on HP UE for Band n34 | Xiaomi |
| 7.42.2 | UE RF requirements | |
| R4-2105016 | Discussion on the PC2 UE RF requirements of NR n39 | CMCC |
| R4-2105017 | Draft CR on PC2 UE RF requirements of n39 in Rel-17 TS 38.101-1 | CMCC |
| R4-2106549 | Discussion on HP UE for Band n39 | Xiaomi |
| 7.43 | Introduction of 900 MHz spectrum to 5G NR applicable for Rail Mobile Radio | |
| R4-2105200 | Email discussion summary for [98-bis-e][127] RAIL_900_1900MHz | Moderator (UIC) |
| R4-2105387 | Way forward on RMR 900MHz and 1900MHz | UIC |
| R4-2105464 | Email discussion summary for [98-bis-e][127] RAIL_900_1900MHz | Moderator (UIC) |
| 7.43.1 | General | |
| R4-2107312 | On RMR 900MHz band | Huawei, HiSilicon |
| 7.44.1 | General | |
| R4-2107313 | On RMR 1900MHz band | Huawei, HiSilicon |
| 8.1.1 | General | |
| R4-2104512 | 3GPP TS 38.151 v0.3.0 | vivo |
| R4-2104515 | Updated workplan of MIMO OTA WI | vivo, CAICT, OPPO |
| R4-2105997 | Email discussion summary for [98-bis-e][326] NR_MIMO_OTA | Moderator (CAICT |
| R4-2106092 | WF on NR MIMO OTA | vivo,CAICT |
| R4-2106093 | TP to TS38.151: revision on MIMO Average Spherical Coverage | Qualcomm Incorporated, Huawei, HiSilicon , CAICT, vivo, OPPO |
| R4-2106096 | Updated workplan of MIMO OTA WI | vivo, CAICT, OPPO |
| R4-2106144 | Email discussion summary for [98-bis-e][326] NR_MIMO_OTA | Moderator (CAICT) |
| R4-2107126 | On Blocking MU for FR2 MIMO OTA | Keysight Technologies UK Ltd |
| 8.1.2.2 | Performance Requirements for FR2 | |
| R4-2104513 | Discussions on FR2 FoM | vivo |
| R4-2106272 | Views on how to treat the missing points for FR2 FoM | CAICT |
| R4-2106568 | FoM for FR2 | OPPO |
| R4-2107116 | Discussion on FR2 MIMO OTA performance requirements | Qualcomm Incorporated |
| R4-2107117 | TP to TS38.151: revision on definaiton fo MASC | Qualcomm Incorporated |
| R4-2107294 | Discussion on FR2 MIMO OTA simulation | HiSilicon Technologies Co. Ltd |
| R4-2107295 | TP to 38.151 on MIMO Average Spherical Coverage | HiSilicon Technologies Co. Ltd |
| R4-2107363 | TP to TS38.151: revision on definition for MASC | Qualcomm Incorporated |
| 8.1.3.1 | Testing parameters for Performance | |
| R4-2104514 | Discussion on Power Validation procedure and compensation process | vivo |
| R4-2105041 | Discussion on channel model and downlink power configuration | Samsung |
| R4-2105169 | Testing parameters for Performance: "On remaining open issues of testing parameters for performance" | Huawei,HiSilicon |
| R4-2107293 | on channel bandwidth for NR FR2 MIMO OTA RMC | HiSilicon Technologies Co. Ltd |
| 8.1.3.2 | Optimization of test methodologies | |
| R4-2104511 | TP to TS38.151 v0.2.0 on calibration and test procedure | vivo, CAICT |
| R4-2105170 | Optimization of test methodologies: "On Channel model for FR1 2x2 MIMO OTA requirements" | Huawei,HiSilicon |
| R4-2106095 | TP to TS38.151 v0.2.0 on calibration and test procedure | vivo, CAICT |
| R4-2106569 | Views on FR2 blocking issue | OPPO |
| R4-2107174 | Views on MU evaluation of FR2 blocking issue | CAICT |
| 8.1.3.3 | Channel model validation | |
| R4-2104510 | TP to TS38.151 v0.2.0 on FR1 Channel model | vivo, CAICT |
| R4-2105020 | NR FR1 MIMO OTA Reference Spatial Correlation Curves based on Different Optimization Algorithm | CMCC |
| R4-2106094 | TP to TS38.151 v0.2.0 on FR1 Channel model | vivo, CAICT |
| R4-2106097 | Reference Channel Emulation Curves | Keysight Technologies UK Ltd |
| R4-2106567 | Consideration on Spatial Correlation with combined beam | OPPO |
| R4-2106902 | Spatial Channel Model Validation Targets | Spirent Communications |
| R4-2107127 | Reference Channel Emulation Curves | Keysight Technologies UK Ltd |
| 8.2 | RF requirements enhancement for NR frequency range 1 (FR1) | |
| R4-2105388 | Way forward on MPR/AMPR requirements for PC2 intra-band UL contiguous CA | Skyworks |
| R4-2105465 | Email discussion summary for [98-bis-e][128] NR_RF_FR1_enh_Part_1 | Moderator (Huawei) |
| 8.2.1 | General and work plan | |
| R4-2105201 | Email discussion summary for [98-bis-e][128]NR_RF_FR1_enh_Part_1 | Moderator (Huawei, HiSilicon) |
| R4-2105389 | Way forward on RF architecture options handling for PC2 intra-band UL NC CA | Huawei, HiSilicon |
| R4-2105390 | Way forward on intra-band UL contiguous CA for UL MIMO | vivo |
| 8.2.2.1 | UL MIMO configuration for SUL band configurations | |
| R4-2104637 | DraftCR to TS 38.101-1 on switching time between SUL and NUL | ZTE Wistron Telecom AB |
| 8.2.2.2 | 2Tx switching between carrier 1 and carrier 2 | |
| R4-2104638 | Further discussion on UL Tx switching in Rel-17 | ZTE Wistron Telecom AB |
| R4-2105087 | MPR for 26 dBm transmissions on switched carriers | Ericsson |
| R4-2105202 | Email discussion summary for [98-bis-e][129] NR_RF_FR1_enh_Part_2 | Moderator (China Telecom) |
| R4-2105466 | Email discussion summary for [98-bis-e][129] NR_RF_FR1_enh_Part_2 | Moderator (China Telecom) |
| 8.2.2.3 | Tx switching between 1 carrier on band A and 2 contiguous aggregated carriers on band B | |
| R4-2104592 | Draft CR to 38.101-1 Correction on DL interruption applicability for inter-band CA | CMCC |
| R4-2104593 | Discussion on DL interruption applicability | CMCC |
| R4-2104639 | draftCR on Rel-17 UL Tx switching time mask for 2Tx-2Tx switching between two carriers and 1Tx-2Tx/2Tx-2Tx switching between two bands in Rel-17 | ZTE Wistron Telecom AB |
| R4-2105488 | Draft CR to 38.101-1 Correction on DL interruption applicability for inter-band CA | CMCC |
| 8.2.2.4 | HPUE for TDD intra-band contiguous UL CA | |
| R4-2104655 | FR1 PC2 Contiguous UL CA Simulation Results | Nokia Corporation |
| R4-2104994 | MPR initial simulation results for NR intra-band contiguous CA according to candidate RF architectures | LG Electronics France |
| R4-2105325 | MPR initial results for NR PC2 intra-band contiguous CA UE according to RF architecture | LG Electronics |
| R4-2106304 | PC2 Class C UL CA UE Architecture and MPR/A-MPR evaluation | Skyworks Solutions Inc. |
| R4-2107260 | on HPUE intra-band contiguous CA MPR | HiSilicon Technologies Co. Ltd |
| R4-2107370 | HPUE MPR with 1PA architecture | Qualcomm Incorporated |
| 8.2.2.5 | HPUE for TDD intra-band non-contiguous UL CA | |
| R4-2104437 | Potential issues on UL Intra band NC CA with 1PA/1LO assumption | Nokia Japan |
| R4-2104819 | Discussion on Transmitter Architecture for PC2 UL NC CA | Skyworks Solutions Inc. |
| R4-2105088 | Power capability and back-off for NC (and contigous) intra-band CA | Ericsson |
| R4-2106366 | On PC2 intra-band non-contiguous NR CA | ZTE Corporation |
| R4-2106542 | Discussion on HP UE for TDD intra-band UL CA | Xiaomi |
| R4-2106543 | LS on UE capability for PC2 TDD intra-band contiguous and non-contiguous CA | Xiaomi |
| R4-2107261 | HPUE intra-band non-contiguous CA architecture | HiSilicon Technologies Co. Ltd |
| R4-2107282 | Discussion on possible reference architecture for nc ul ca | Qualcomm Incorporated |
| 8.2.2.6 | Intra-band UL contiguous CA for UL MIMO (n41C and n78C) | |
| R4-2104956 | Requirements analysis for Intra-band UL contiguous CA for UL-MIMO | vivo |
| R4-2106562 | R17 FR1 UL CA with MIMO | OPPO |
| R4-2107274 | RF requirements for intra-band UL CA for UL MIMO | HiSilicon Technologies Co. Ltd |
| R4-2107278 | draft CR on contiguous CA with UL MIMO for power class 3 | HiSilicon Technologies Co. Ltd |
| 8.3.1 | General and work plan | |
| R4-2104559 | Add beam management type after particular band combination requirement | MediaTek Beijing Inc. |
| R4-2105203 | Email discussion summary for [98-bis-e][130] NR_RF_FR2_req_enh2_Part_1 | Moderator (Nokia) |
| R4-2105391 | Way forward on IBM Requirements | Nokia, Nokia Shanghai Bell |
| R4-2105392 | Way forward on UE requirements for CA configurations based on CBM | Qualcomm |
| R4-2105393 | Way forward on Inter-band UL CA | Samsung |
| R4-2105467 | Email discussion summary for [98-bis-e][130] NR_RF_FR2_req_enh2_Part_1 | Moderator (Nokia) |
| R4-2105495 | FR2 inter-band CA for different frequency band groups with IBM (TP to TS 38.851 | Nokia, Nokia Shanghai Bell, NTT DOCOMO, INC. |
| 8.3.2.1 | Inter-band DL CA enhancements | |
| R4-2106287 | Discussion on RF requirements for inter-band DL CA based on CBM and IBM | LG Electronics Polska |
| 8.3.2.1.1 | Applicability of CBM/IBM for different CA configurations | |
| R4-2104490 | Draft CR to 38.101-2 on requirements for UEs that support inter-band CA with CBM | Qualcomm Incorporated |
| R4-2104491 | Requirement framework for Inter-band CA with CBM | Qualcomm Incorporated |
| R4-2105095 | Applicability of CBM/IBM for different CA configurations | Xiaomi |
| R4-2106364 | Discussion on CBM&IBM for FR2 Inter-band DL CA | ZTE Corporation |
| R4-2107108 | Discussion on FR2 inter-band DL CA with CBM and IBM | Google Inc. |
| 8.3.2.1.2 | UE requirements for CA configurations CA_n258A-n260A and CA_n257A-n259A based on IBM | |
| R4-2104561 | RIB proposal of CA_n258A-n260A and CA_n257A-n259A based on IBM | MediaTek Beijing Inc. |
| R4-2104698 | UE requirements for CA based on IBM | Sony, Ericsson |
| R4-2104715 | FR2 inter-band CA for different frequency band groups with IBM | Nokia, Nokia Shanghai Bell |
| R4-2105096 | Rx requirements for CA_n258A-n260A and CA_n257A-n259A based on IBM | Xiaomi |
| R4-2106346 | Band specific requirements for DL CA_n257-n259 including TP for TR 38.851 | NTT DOCOMO INC. |
| R4-2106365 | Discussion on UE requirements for CA configurations of CA_n258-n260 and CA_n257-n259 based on IBM | ZTE Corporation |
| R4-2106565 | R17 FR2 Inter-band DL CA with IBM | OPPO |
| 8.3.2.1.3 | UE requirements for CA configurations within the same frequency group based on CBM | |
| R4-2104401 | UE RF CBM requirements for CA configurations within same frequency group | Nokia, Nokia Shanghai Bell |
| R4-2104524 | Discussion on EIS spherical coverage and Fs,inter for CBM | vivo |
| R4-2104562 | Introduce Fs_inter_CBM as UE capability for inter-band DL CA based on CBM | MediaTek Beijing Inc. |
| R4-2104699 | UE requirements for CA based on CBM | Sony, Ericsson |
| R4-2105097 | Rx requirements for inter-band DL CA within the same frequency groups based on CBM | Xiaomi |
| R4-2106564 | R17 FR2 Inter-band DL CA within same frequency group based on CBM | OPPO |
| R4-2107262 | inter-band CA DL CA with CBM | HiSilicon Technologies Co. Ltd |
| 8.3.2.2 | Inter-band UL CA | |
| R4-2104525 | Discussion on per UE concept of FR2 UL CA | vivo |
| R4-2106289 | Discussion on RF requirements for inter-band UL CA based on IBM | LG Electronics Polska |
| 8.3.2.2.1 | UE requirements for CA configuration CA_n257A-n259A based on IBM | |
| R4-2104560 | Proposal on inter-band UL CA requirement framework | MediaTek Beijing Inc. |
| R4-2104706 | UE UL CA requirements based on IBM | Sony, Ericsson |
| R4-2104716 | On FR2 inter-band UL CA for different frequency group based on IBM | Nokia, Nokia Shanghai Bell |
| R4-2104918 | Definition of Max EIRP limit for FR2 ULCA | Qualcomm Incorporated |
| R4-2105098 | Tx requirements for inter-band UL CA for two bands between different frequency groups based on IBM | Xiaomi |
| R4-2106402 | UE requirements for FR2 UL Inter-band CA from the perspective of Japanese regulations | NTT DOCOMO, INC., SoftBank Corp., KDDI Corporation, Rakuten Mobile, Inc |
| R4-2106563 | R17 FR2 Inter-band UL CA | OPPO |
| 8.3.3.1 | Inter-band DL CA enhancements | |
| R4-2106290 | Discussion on feasibility for inter-band DL CA | LG Electronics Polska |
| 8.3.3.1.1 | Feasibility study for CA configurations within same frequency group based on IBM | |
| R4-2104400 | UE RF IBM requirements for CA configurations within same frequency group | Nokia, Nokia Shanghai Bell |
| R4-2105099 | The feasibility of inter-band CA within the same frequency group for IBM | Xiaomi |
| R4-2107265 | inter-band CA DL CA with IBM | HiSilicon Technologies Co. Ltd |
| 8.3.3.1.2 | Feasibility study for CA configurations between different frequency groups based on CBM | |
| R4-2105042 | Discussion on CBM inter-band CA | Samsung |
| R4-2105100 | The feasibility of inter-band CA between different frequency groups for CBM | Xiaomi |
| 8.3.4 | UL gaps for self-calibration and monitoring | |
| R4-2105205 | Email discussion summary for [98-bis-e][132] NR_RF_FR2_req_enh2_Part_3 | Moderator (Apple) |
| R4-2105394 | Way forward on UL gap for FR2 | Apple |
| R4-2105469 | Email discussion summary for [98-bis-e][132] NR_RF_FR2_req_enh2_Part_3 | Moderator (Apple) |
| 8.3.4.1 | Gap use cases and performance evaluation | |
| R4-2104526 | Discussion on gap for PA calibration | vivo |
| R4-2104610 | the evaluation metrics for performance gain | CMCC |
| R4-2104849 | UL gaps for Tx power management | Apple |
| R4-2104920 | Discussion on UL gap for self-calibration and monitoring | ZTE Corporation |
| R4-2105089 | Open issues for UL gaps for Body Proximity Sensing (BPS) and calibration | Ericsson, Sony |
| R4-2106396 | UE FR2 UL Gap for P-MPR/EIRP enhancements | Nokia, Nokia Shanghai Bell |
| R4-2107034 | Consideration on FR2 UL gap for self-calibration | NTT DOCOMO INC. |
| R4-2107267 | On FR2 UL gap for coherence calibration | HiSilicon Technologies Co. Ltd |
| R4-2107269 | on FR2 UL gap for transceiver calibration | HiSilicon Technologies Co. Ltd |
| R4-2107279 | UL calibration gap performance improvement and fall back behavior | Qualcomm Incorporated |
| 8.3.4.2 | Others | |
| R4-2107280 | UL cal gap types and applicability | Qualcomm Incorporated |
| 8.3.5 | Support of contiguous downlink aggregated channel BW up to 1600 MHz | |
| R4-2105204 | Email discussion summary for [98-bis-e][131] NR_RF_FR2_req_enh2_Part_2 | Moderator (Qualcomm) |
| R4-2105395 | Way forward on DC location parameters | ZTE Corporation |
| R4-2105396 | Way forward on new CA BW class notation | ZTE Corporation |
| R4-2105397 | Draft CR on CA BW class 1600 MHz for fallback group 2 | Xiaomi |
| R4-2105468 | Email discussion summary for [98-bis-e][131] NR_RF_FR2_req_enh2_Part_2 | Moderator (Qualcomm) |
| 8.3.5.1 | New FR2 CA BW classes | |
| R4-2104691 | Discussion on RRM requirements for FR2 inter-band DL CA | Xiaomi |
| R4-2105101 | Introducing new bandwidth classes for FR2 CA | Xiaomi |
| R4-2106907 | New FR2 CA BW classes | Apple |
| R4-2107266 | on FR2 CA bandwidth class | HiSilicon Technologies Co. Ltd |
| 8.3.5.2 | UE Rx requirements | |
| R4-2105102 | Rx requirements for new bandwidth classes | Xiaomi |
| 8.3.6 | DC location reporting scheme for intra-band UL CA with more than 2 CCs for both FR2 and FR1 | |
| R4-2106566 | R17 DC reporting for more than 2CCs | OPPO |
| R4-2106910 | DC location for intra-band UL CA with more than 2 CCs | Apple |
| R4-2107257 | Further study on DC location reporting | HiSilicon Technologies Co. Ltd |
| R4-2107281 | DC location for greater than 2CC | Qualcomm Incorporated |
| 8.3.7 | RRM core requirements | |
| R4-2105685 | Email discussion summary for [98-bis-e][215] NR_RF_FR2_req_enh2_RRM | Moderator (Nokia, Nokia Shanghai Bell) |
| R4-2105785 | WF on the RRM requirements or FR2 Inter-band DL CA and UL CA | Nokia |
| R4-2105817 | Email discussion summary for [98-bis-e][215] NR_RF_FR2_req_enh2_RRM | Moderator (Nokia, Nokia Shanghai Bell) |
| 8.3.7.1 | Inter-band DL CA enhancements | |
| R4-2104632 | Considerations on RRM requirements for inter-band DL CA in NR FR2 | vivo |
| R4-2104837 | On the feasiblity of CBM with MRTD more than CP length | Apple |
| R4-2104978 | Discussion on FR2 inter-band DL CA enhancements | NEC |
| R4-2105141 | Support up to 3 us MRTD | Ericsson |
| R4-2106302 | Discussion on MRTD requirements for FR2 inter-band CA based on CBM and IBM | LG Electronics Polska |
| R4-2106393 | Discussion on FR2 RF RRM | Nokia, Nokia Shanghai Bell |
| R4-2106394 | DraftCR for CBM and IBM applicability | Nokia, Nokia Shanghai Bell |
| R4-2106506 | Discussion on MRTD requirements for inter-band DL CA in FR2 | Intel Corporation |
| R4-2106531 | RRM requirements for FR2 inter-band DL CA enhancements | OPPO |
| R4-2106944 | Discussion on FR2 inter-band DL CA enhancement | Huawei, HiSilicon |
| R4-2107289 | FR2 Inter-band DL CA | Qualcomm Incorporated |
| 8.3.7.2 | Inter-band UL CA | |
| R4-2106945 | Discussion on FR2 inter-band UL CA | Huawei, HiSilicon |
| 8.3.7.3 | UL gaps for self-calibration and monitoring | |
| R4-2106395 | UL Gaps for PA calibration and proximity detection | Nokia, Nokia Shanghai Bell |
| R4-2106946 | Discussion on UL gaps for self-calibration and monitoring | Huawei, HiSilicon |
| R4-2107078 | Discussion on RRM impact of UL gaps for self-calibration and monitoring | vivo |
| 8.4 | Further RRM enhancement for NR and MR-DC | |
| R4-2105686 | Email discussion summary for [98-bis-e][216] NR_RRM_enh2_1 | Moderator (Apple) |
| R4-2105818 | Email discussion summary for [98-bis-e][216] NR_RRM_enh2_1 | Moderator (Apple) |
| R4-2105819 | Email discussion summary: [98-bis-e][216] NR_RRM_enh2_1 | Moderator (Apple) |
| R4-2105830 | LS on RACH procedure for HO with PSCell | Ericsson |
| 8.4.2.1 | SRS antenna port switching | |
| R4-2104565 | Discussion on SRS antenna port switching | MediaTek inc. |
| R4-2104694 | Discussion on SRS antenna switching interruption requirements | Xiaomi |
| R4-2104758 | Further discussion on SRS antenna port switching | CATT |
| R4-2104831 | On SRS antenna port switching | Apple |
| R4-2104909 | SRS antenna switching discussion | Qualcomm, Inc. |
| R4-2104945 | Discussion on SRS antenna port switching | CMCC |
| R4-2104979 | Discussion on SRS antenna port switching | NEC |
| R4-2104991 | Discussion on interruption due to SRS antenna port switching | LG Electronics Inc. |
| R4-2105786 | WF on further RRM enhancement for NR and MR-DC – SRS antenna port switching | Apple |
| R4-2106409 | Discussion on the interruption requirements at SRS antenna port switching | Nokia, Nokia Shanghai Bell |
| R4-2106462 | Discussion about SRS antenna port switching | Intel Corporation |
| R4-2106532 | RRM requirements for SRS ant port switch | OPPO |
| R4-2106881 | On RRM requirements for SRS antenna port switching | Ericsson |
| R4-2106986 | Discussion on requirements for SRS antenna switching | Huawei, HiSilicon |
| R4-2107079 | Discussion on RRM requirements for SRS antenna port switching | vivo |
| 8.4.2.2 | HO with PSCell | |
| R4-2104685 | Discussion on RRM requirements for handover with PSCell | Xiaomi |
| R4-2104759 | Further discussion on HO with PSCell | CATT |
| R4-2104832 | On RRM requirement for handover with PSCell | Apple |
| R4-2104932 | Views on Procedures of HO with PSCell | NTT DOCOMO, INC. |
| R4-2104943 | Discussion on HO with PSCell | CMCC |
| R4-2104980 | Discussion on PSCell HO | NEC |
| R4-2105787 | WF on further RRM enhancement for NR and MR-DC – Handover with PSCell | Apple |
| R4-2106463 | Discussion about HO with PSCell | Intel Corporation |
| R4-2106533 | RRM requirements for HO with PSCell | OPPO |
| R4-2106882 | On handover with PSCell | Ericsson |
| R4-2106924 | Discussion on handover with PSCell | ZTE Corporation |
| R4-2106987 | Discussion on requirements for HO with PSCell | Huawei, HiSilicon |
| R4-2107080 | Discussion on RRM requirements for HO with PSCell | vivo |
| R4-2107123 | Discussion on HO with PSCell | MediaTek inc. |
| R4-2107224 | discussion on HO with PSCell | Nokia, Nokia Shanghai Bell |
| R4-2107249 | Discussion on timelines of HO with PSCell | Qualcomm CDMA Technologies |
| 8.4.2.3 | PUCCH SCell activation/deactivation | |
| R4-2104564 | Discussion on PUCCH SCell activation and deactivation | MediaTek inc. |
| R4-2104633 | Regarding PUCCH SCell activation and deactivation | vivo |
| R4-2104686 | Discussion on SCell activation and deactication requirements for PUCCH Scell | Xiaomi |
| R4-2104760 | Further discussion on PUCCH SCell activation_deactivation | CATT |
| R4-2104833 | On PUCCH SCell activation and deactivation | Apple |
| R4-2104944 | Discussion on PUCCH SCell activation/deactivation | CMCC |
| R4-2104981 | Discussion on PUCCH SCell activation | NEC |
| R4-2105104 | Discussions on PUCCH SCell Activation/Deactivation delay requirements | NTT DOCOMO, INC. |
| R4-2105687 | Email discussion summary for [98-bis-e][217] NR_RRM_enh2_2 | Moderator (CATT) |
| R4-2105788 | WF on further RRM enhancement for NR and MR-DC – PUCCH SCell activation/deactivation requirements | CATT |
| R4-2106408 | Discussion on the activation delay for deactivated PUCCH SCell | Nokia, Nokia Shanghai Bell |
| R4-2106534 | RRM requirements for PUCCH SCell ActivationDeactivation | OPPO |
| R4-2106883 | On SCell (de)activation with PUCCH | Ericsson |
| R4-2106988 | Discussion on requirements for PUCCH SCell activation | Huawei, HiSilicon |
| R4-2107290 | Discussion on PUCCH SCell Activation | Qualcomm Incorporated |
| 8.5 | NR and MR-DC measurement gap enhancements | |
| R4-2105842 | Email discussion summary: [98-bis-e][218] NR_MG_enh_1 | Moderator (MediaTek) |
| R4-2105846 | Email discussion summary: [98-bis-e][219] NR_MG_enh_2 | Moderator (Intel Corporation) |
| 8.5.1 | General and work plan | |
| R4-2104581 | Work plan of R17 NR and MR-DC measurement gap enhancements WI | MediaTek inc. |
| R4-2105688 | Email discussion summary for [98-bis-e][218] NR_MG_enh_1 | Moderator (MediaTek inc.) |
| R4-2105790 | Work plan of R17 NR and MR-DC measurement gap enhancements WI | MediaTek inc. |
| 8.5.2.1 | Pre-configured MG pattern(s) | |
| R4-2104582 | Pre-configured MG pattern(s) per configured BWP | MediaTek inc. |
| R4-2104635 | On pre configured MG patterns | vivo |
| R4-2104687 | Discussion on pre-configured MG pattern for NR | Xiaomi |
| R4-2104750 | Discussion on pre-configured MG pattern | CATT |
| R4-2104854 | Consideration on preconfigured measurement gap patterns | Apple |
| R4-2104921 | Views on pre-configured MG patterns | ZTE Corporation |
| R4-2104936 | Discussion on pre-configured MG pattern(s) | CMCC |
| R4-2104983 | Discussion on preconfigured measurement gap | NEC |
| R4-2105689 | Email discussion summary for [98-bis-e][219] NR_MG_Part_2 | Moderator (Intel Corporation) |
| R4-2105791 | WF on R17 NR MG enhancements – Pre-configured MG | Intel Corporation |
| R4-2106446 | Discussion on pre-configured measurement gap | Intel Corporation |
| R4-2106535 | On pre-configured MG pattern(s) for NR_MG_enh | OPPO |
| R4-2107027 | Discussion on pre-configured MG | Huawei, HiSilicon |
| R4-2107151 | Analysis of requirements for pre-configured measurement gap pattern | Ericsson |
| R4-2107175 | Discussion on Pre-configured MG patterns | Nokia, Nokia Shanghai Bell |
| R4-2107347 | Realizing pre-configured MG via network controlled fast gap(NCFG) | Qualcomm CDMA Technologies |
| 8.5.2.2 | Multiple concurrent and independent MG patterns | |
| R4-2104583 | Multiple concurrent and independent gap patterns | MediaTek inc. |
| R4-2104636 | Consideration on multiple concurrent and independent MG patterns | vivo |
| R4-2104688 | Discussion on multiple concurrent and independent MG patterns for NR | Xiaomi |
| R4-2104751 | Discussion on multiple concurrent and independent MG patterns | CATT |
| R4-2104855 | Discussion on multiple concurrent and independent MG patterns | Apple |
| R4-2104933 | Discussion on multiple concurrent and independent MG patterns | CMCC |
| R4-2104982 | Discussion on concurrent and independent MG | NEC |
| R4-2105789 | WF on R17 NR MG enhancements - Multiple concurrent and independent MG patterns | MediaTek |
| R4-2105856 | WF on R17 NR MG enhancements - Multiple concurrent and independent MG patterns | MediaTek |
| R4-2106303 | Discussion on multiple concurrent and independent MG patterns | LG Electronics Polska |
| R4-2106344 | Discussion on mulitple concurrent and independent MG patterns | Qualcomm Incorporated |
| R4-2106392 | Discussion on concurrent and independent MG patterns | Nokia, Nokia Shanghai Bell |
| R4-2106447 | Discussion on multiple and independent concurrent measurement gaps in NR | Intel Corporation |
| R4-2106536 | On multiple concurrent and independent MG patterns for NR_MG_enh | OPPO |
| R4-2106880 | On parallel measurement gap patterns | Ericsson |
| R4-2106923 | Discussion on independent and concurrent MGs | ZTE Corporation |
| R4-2107028 | Discussion on multiple concurrent MGs | Huawei, HiSilicon |
| 8.5.2.3 | Network Controlled Small Gap | |
| R4-2104584 | Network Controlled Small Gap | MediaTek inc. |
| R4-2104634 | On network controlled small gap | vivo |
| R4-2104752 | Discussion on Network Controlled Small Gap (NCSG) | CATT |
| R4-2104856 | On network controlled small gap | Apple |
| R4-2104934 | Discussion on Network Controlled Small Gap | CMCC |
| R4-2105792 | WF on R17 NR MG enhancements – NCSG | Intel Corporation |
| R4-2106448 | Discussion on NCSG in NR | Intel Corporation |
| R4-2106537 | On NCSG for NR_MG_enh | OPPO |
| R4-2107029 | Discussion on NCSG | Huawei, HiSilicon |
| R4-2107152 | Analysis of requirements for network controlled small gap | Ericsson |
| R4-2107176 | Discussion on Network Controlled Small Gaps for NR | Nokia, Nokia Shanghai Bell |
| R4-2107318 | Discussion on open issues of network controlled small gap for NR | Qualcomm CDMA Technologies |
| 8.6.1 | General and work plan | |
| R4-2104946 | Updated work plan for enhancement for NR high speed train scenario in FR1 | CMCC |
| R4-2105690 | Email discussion summary for [98-bis-e] [220] NR_HST_FR1_enh_RRM | Moderator (CMCC) |
| R4-2105820 | Email discussion summary for [98-bis-e] [220] NR_HST_FR1_enh_RRM | Moderator (CMCC) |
| 8.6.2.1 | UE RRM core requirements for CA scenario | |
| R4-2104566 | Discussion on Rel-17 HST in FR1 | MediaTek inc. |
| R4-2104753 | Discussion on HST RRM for CA in FR1 | CATT |
| R4-2104812 | On SCell RRM enhancement for NR high speed train scenario in FR1 | Ericsson |
| R4-2104813 | On SCell RRM enhancement for NR high speed train scenario in FR1 | Ericsson |
| R4-2104857 | On R17 FR1 HST RRM measurement requirement | Apple |
| R4-2104904 | FR1 HST RRM discussion | Qualcomm, Inc. |
| R4-2104935 | Discussion on NR HST RRM enhancement for FR1 CA scenario | CMCC |
| R4-2105793 | WF on RRM for FR1 HST | CMCC |
| R4-2106538 | RRM requirement for Rel17 FR1 HST | OPPO |
| R4-2106936 | Discussion on Enhancement for NR high speed train scenario in FR1 | Huawei, HiSilicon |
| R4-2107081 | Discussion on R17 NR FR1 HST RRM requirements | vivo |
| R4-2107250 | Discussion on NR FR1 HST RRM open issues for CA | Nokia, Nokia Shanghai Bell |
| 8.6.3 | UE demodulation requirements (38.101-4) | |
| R4-2105992 | Email discussion summary for [98-bis-e][321] NR_HST_FR1_Demod | Moderator (CMCC) |
| 8.6.3.1 | General | |
| R4-2106098 | WF on FR1 HST demodulation | CMCC |
| R4-2106099 | Summary for FR1 HST demodulation results | Ericsson |
| R4-2106145 | Email discussion summary for [98-bis-e][321] NR_HST_FR1_Demod | Moderator (CMCC) |
| 8.6.3.2 | PDSCH requirements for CA scenarios | |
| R4-2104844 | On PDSCH CA Requirements in HST | Apple |
| R4-2104939 | Simulation results for HST-SFN joint transmission for CA scenario | CMCC |
| R4-2104948 | Discussion on FR1 HST UE demodulation for CA scenario | CMCC |
| R4-2104976 | Views on HST CA tests for FR1 | NTT DOCOMO, INC. |
| R4-2106001 | On PDSCH CA Requirements in HST | Apple |
| R4-2106431 | Views on HST CA PDSCH performance requirements | Intel Corporation |
| R4-2106808 | Discussion on PDSCH CA scenarios for NR UE HST FR1 performance requirements | Huawei, HiSilicon |
| R4-2106809 | Simulation results for PDSCH CA scenarios for NR UE HST FR1 performance requirements | Huawei, HiSilicon |
| R4-2106862 | Initial simulation result of PDSCH for CA in HST | Ericsson |
| R4-2106863 | PDSCH demodulation requirements for CA with HST-SFN scenario | Ericsson |
| R4-2107041 | Views on FR1 HST PDSCH CA Tests | Qualcomm Incorporated |
| 8.6.3.3 | Enhanced transmission schemes | |
| R4-2104845 | On Enhanced transmission schemes for HST | Apple |
| R4-2106432 | Views on HST PDSCH performance requirements for multi-DCI based Tx scheme | Intel Corporation |
| R4-2106810 | Discussion on enhanced transmission schemes for NR UE HST FR1 performance requirements | Huawei, HiSilicon |
| R4-2106811 | Simulation results for evaluations of enhanced transmission schemes for NR UE HST FR1 performance requirements | Huawei, HiSilicon |
| R4-2106864 | PDSCH demodulation requirements with enhanced transmission schemes in HST scenario | Ericsson |
| R4-2107043 | Views on FR1 HST Enhanced Transmission Schemes | Qualcomm Incorporated |
| R4-2107092 | Discussion on multi-DCI transmission scheme for FR1 HST | MediaTek inc. |
| 8.7.1 | General and work plan | |
| R4-2105206 | Email discussion summary for [98-bis-e][133] NR_HST_FR2 | Moderator (Samsung) |
| R4-2105398 | Way forward on UE RF requirement for FR2 HST | Samsung |
| R4-2105399 | TR for FR2 HST | Nokia, Nokia Shanghai Bell, Samsung |
| R4-2105470 | Email discussion summary for [98-bis-e][133] NR_HST_FR2_enh | Moderator (Samsung) |
| R4-2105491 | Way forward on UE RF requirement for FR2 HST | Samsung |
| R4-2106397 | TR for FR2 HST | Nokia, Nokia Shanghai Bell, Samsung |
| R4-2106825 | Discussion on general issues for NR FR2 HST deployment scenario | Huawei, HiSilicon |
| 8.7.2 | High speed train deployment scenario in FR2 | |
| R4-2104905 | FR2 HST deployment scenario discussion | Qualcomm, Inc. |
| R4-2105993 | Email discussion summary for [98-bis-e][322] NR_HST_FR2_Scenarios_Demod | Moderator (Samsung) |
| R4-2106100 | WF on FR2 HST Deployment Scenario Analysis | Samsung |
| R4-2106101 | WF on Channel Modeling for FR2 HST | Nokia |
| R4-2106146 | Email discussion summary for [98-bis-e][322] NR_HST_FR2_Scenarios_Demod | Moderator (Samsung) |
| 8.7.2.1 | Deployment Scenario-A | |
| R4-2104679 | On HST deployment aspects in scenario A | Ericsson |
| R4-2104924 | NR support for high speed train scenario in FR2 - Deployment Scenario-A | ZTE Corporation |
| R4-2105023 | Discussion on FR2 HST Deployment Scenario-A | Samsung |
| R4-2106102 | WF on Demodulation requirement for FR2 HST | Samsung |
| R4-2106503 | Discussion on FR2 HST deployment aspects | Intel Corporation |
| R4-2106693 | On HST FR2 Deployment Scenario A | Nokia, Nokia Shanghai Bell |
| R4-2106826 | Discussion on NR FR2 HST deployment Scenario-A | Huawei, HiSilicon |
| 8.7.2.2 | Deployment Scenario-B | |
| R4-2104680 | On HST deployment aspects in Scenario B | Ericsson |
| R4-2104926 | NR support for high speed train scenario in FR2 - Deployment Scenario-B | ZTE Corporation |
| R4-2105024 | Discussion on FR2 HST Deployment Scenario-B | Samsung |
| R4-2106694 | On HST FR2 Deployment Scenario B | Nokia, Nokia Shanghai Bell |
| R4-2106827 | Discussion on NR FR2 HST deployment Scenario-B | Huawei, HiSilicon |
| 8.7.2.3 | Channel modeling | |
| R4-2104678 | Channel model for FR2 HST scenario | Ericsson |
| R4-2105025 | Channel modeling for FR2 HST and TP to TR 38.854 | Samsung |
| R4-2106828 | Discussion on channel modeling for NR FR2 HST | Huawei, HiSilicon |
| R4-2106911 | On HST FR2 Channel Modelling | Nokia, Nokia Shanghai Bell |
| 8.7.2.4 | Others | |
| R4-2104677 | On available capacity and the number of UE per train | Ericsson |
| R4-2104925 | Other considerations for HST_FR2 | ZTE Corporation |
| 8.7.3 | UE RF core requirements | |
| R4-2104906 | FR2 HST RF discussion | Qualcomm, Inc. |
| 8.7.3.1 | Baseline power class and UE RF requirement | |
| R4-2104585 | Consideration on UE beam and pwr requirements for FR2 HST | Ericsson France S.A.S |
| R4-2104719 | UE power class for FR2 HST | Nokia, Nokia Shanghai Bell |
| R4-2105026 | On baseline power class and UE RF requirement for FR2 HST | Samsung |
| 8.7.3.2 | Beam correspondence | |
| R4-2104586 | Considerations on Beam correspondance for HST FR2 Ues | Ericsson France S.A.S |
| R4-2104720 | UE beam correspondence for FR2 HST | Nokia, Nokia Shanghai Bell |
| R4-2104923 | Discussion on PDSCH requirements for CA in FR1 HST | ZTE Corporation |
| R4-2106333 | On Beam Correspondence Requirement for FR2 HST UE | Samsung |
| 8.7.4 | RRM core requirements | |
| R4-2104907 | FR2 HST RRM discussion | Qualcomm, Inc. |
| R4-2105691 | Email discussion summary for [98-bis-e][221]NR_HST_FR2_RRM | Moderator (Nokia, Nokia Shanghai Bell) |
| R4-2105794 | WF on FR2 HST RRM requirements | Nokia, Nokia Shanghai Bell |
| R4-2105821 | Email discussion summary for [98-bis-e][221]NR_HST_FR2_RRM | Moderator (Nokia, Nokia Shanghai Bell) |
| 8.7.4.1 | General | |
| R4-2104754 | Discussion on the maximum supported speed analysis for NR HST FR2 | CATT |
| R4-2104814 | RRM general considerations for HST FR2 | Ericsson |
| R4-2104851 | Discussion on FR2 HST RRM requirement - geneal | Apple |
| R4-2105027 | Maximum Supported Speed from RRM perspective for FR2 HST | Samsung |
| R4-2106505 | General aspects of RRM requirements for HST in FR2 | Intel Corporation |
| R4-2106583 | Simulation analysis for HST in FR2 | Nokia, Nokia Shanghai Bell |
| 8.7.4.2 | RRM requirements for FR2 HST | |
| R4-2104755 | Discussion on RRM requirements for NR FR2 HST | CATT |
| R4-2104815 | RRM requirements for HST FR2 | Ericsson |
| R4-2104852 | Discussion on RRM requirement for FR2 HST | Apple |
| R4-2104949 | Discussion on RRM requirements for FR2 HST | CMCC |
| R4-2106504 | RRM requirements for HST in FR2 | Intel Corporation |
| R4-2106584 | Discussion about RRM requirements for HST in FR2 | Nokia, Nokia Shanghai Bell |
| R4-2106836 | Further discussion on RRM requirements for FR2 HST | BEIJING SAMSUNG TELECOM R&D |
| R4-2106838 | Further discussion on RRM requirements for FR2 HST | Samsung |
| R4-2106937 | Discussion on NR support for high speed train scenario in FR2 | Huawei, HiSilicon |
| 8.7.5.1 | General | |
| R4-2105028 | Maximum Supported Speed from Demod perspective for FR2 HST | Samsung |
| R4-2106435 | Analysis on max supported speed for HST FR2 demodulation requirements | Intel Corporation |
| R4-2106473 | Preliminary observations on FR2 HST UE Demod Performance Test | Qualcomm Incorporated |
| R4-2106829 | Discussion on general issues for NR FR2 HST demodulation requirements | Huawei, HiSilicon |
| R4-2106865 | HST single tap channel profile for unidirectional deployment | Ericsson |
| R4-2106916 | On HST FR2 Maximum Supported Speed from Demodulation Perspective | Nokia, Nokia Shanghai Bell |
| 8.7.5.2 | UE demodulation requirements | |
| R4-2105029 | View on UE demodulation requirement for Rel-17 FR2 HST | Samsung |
| R4-2106436 | View on UE demodulation requirements for HST FR2 | Intel Corporation |
| R4-2106830 | Discussion on UE demodulation requirements for FR2 HST | Huawei, HiSilicon |
| R4-2106866 | UE demodulation requirements for HST FR2 | Ericsson |
| 8.7.5.3 | BS demodulation requirements | |
| R4-2104681 | HST FR2 BS demodulation aspects | Ericsson |
| R4-2105030 | View on BS demodulation requirement for Rel-17 FR2 HST | Samsung |
| R4-2106437 | View on BS demodulation requirements for HST FR2 | Intel Corporation |
| R4-2106780 | On FR2 HST BS demodulation requirements | Nokia, Nokia Shanghai Bell |
| R4-2106831 | Discussion on BS demodulation requirements for FR2 HST | Huawei, HiSilicon |
| 8.8.1 | General and work plan | |
| R4-2104879 | NR_NTN_solutions work plan | THALES |
| R4-2105978 | Email discussion summary for [98-bis-e][307] NTN_Solutions_Part1 | Moderator (THALES) |
| R4-2106103 | WF on [307] NTN_Solutions_Part1 | Thales |
| R4-2106147 | Email discussion summary for [98-bis-e][307] NTN_Solutions_Part1 | Moderator (Thales) |
| R4-2107217 | On the FR2 NTN coexistence scenarios | Hughes/EchoStar, Inmarsat, Thales, ESA, Intelsat |
| 8.8.1.1 | System parameters | |
| R4-2106607 | Discussion on system parameters for NTN | ZTE Corporation |
| R4-2106899 | Reference points and reference model for NTN | Ericsson |
| R4-2107193 | On NTN System parameters | Nokia, Nokia Shanghai Bell |
| 8.8.1.2 | NTN architecture | |
| R4-2104808 | on NTN architecture and RF requirements | CATT |
| R4-2106545 | Discussion on RF interfaces for NR to support non-terrestrial networks | Xiaomi |
| R4-2106608 | Discussion on NTN architecture | ZTE Corporation |
| R4-2106686 | Further discussion on Network architecture on NTN system | Huawei, HiSilicon |
| R4-2107263 | NTN Architecture Aspects | THALES |
| 8.8.1.3 | Regulatory information | |
| R4-2106897 | NTN - Regulatory and spectrum aspects | Ericsson |
| 8.8.2 | Coexistence aspects | |
| R4-2105045 | Simulation assumptions for FR1 coexistence study | Samsung |
| R4-2105046 | Initial simulation results of some NR-NTN co-ex scenarios | Samsung |
| R4-2105979 | Email discussion summary for [98-bis-e][308] NTN_Solutions_Part2 | Moderator (Samsung) |
| R4-2106104 | WF on [308] NTN_Solutions_Part2 | Samsung |
| R4-2106105 | Simulation assumptions for NTN co-existence | Samsung, CATT |
| R4-2106106 | Simulation assumptions for HAPS co-existence | Nokia |
| R4-2106148 | Email discussion summary for [98-bis-e][308] NTN_Solutions_Part2 | Moderator (Samsung) |
| R4-2107270 | On the S-band NTN coexistence scenarios and simulation parameters | THALES |
| 8.8.2.1 | Coexistence scenarios and Simulation assumptions | |
| R4-2106000 | Simulation assumptions for NR NTN co-existence study | Qualcomm Incorporated |
| R4-2106476 | Simulation assumptions for NTN co-existence | CATT |
| R4-2106609 | Further discussion on simulation assumptions for NTN | ZTE Corporation |
| R4-2106684 | Further discussion on NTN simulation assumptions | Huawei, HiSilicon |
| R4-2106898 | NTN Simulations assumptions | Ericsson |
| R4-2107120 | Simulation assumptions for NR NTN co-existence study | Qualcomm Incorporated |
| R4-2107194 | HAPS simulation assumptions for coexistence study | Nokia, Nokia Shanghai Bell |
| 8.8.2.2 | Simulation results | |
| R4-2106544 | Preminary simulation result for coexistence study on NR to support non-terrestrial networks | Xiaomi |
| R4-2106685 | Initial analysis and results about the NTN simulation | Huawei, HiSilicon |
| R4-2106901 | NTN - simulation results for alignment | Ericsson |
| R4-2107121 | Simulation restuls for NTN co-existence calibtartion | Qualcomm Incorporated |
| R4-2107195 | HAPS adjacent channel coexistence simulation results | Nokia, Nokia Shanghai Bell |
| 8.8.3 | RF requirements | |
| R4-2105980 | Email discussion summary for [98-bis-e][309] NTN_Solutions_Part3 | Moderator (CATT) |
| R4-2106107 | draft LS reply on NTN UL time and frequency synchronization requirements | CATT |
| R4-2106149 | Email discussion summary for [98-bis-e][309] NTN_Solutions_Part3 | Moderator (CATT) |
| R4-2106174 | draft LS reply on NTN UL time and frequency synchronization requirements | CATT |
| R4-2107275 | NTN UL frequency synchronization requirement | THALES |
| 8.8.3.1 | Network side requirements | |
| R4-2104761 | Initial consideration on NTN-BS requirements | CATT |
| R4-2106610 | Discussion on RF requirements from satellite network perspective | ZTE Corporation |
| 8.8.3.2 | UE requirements | |
| R4-2104762 | Discussion on RF requirements for NTN UE | CATT |
| R4-2106361 | Discussion on UE UL frequency synchronization requirements in NTN | MediaTek inc. |
| R4-2106900 | Reply LS to RAN4 on NTN UL time and frequency synchronization requirements (frequency) | Ericsson |
| R4-2107122 | Frequency synchronization requirements in NTN | Qualcomm Incorporated |
| 8.8.4 | RRM core requirements | |
| R4-2105795 | WF on NR NTN RRM general and measurement requirements | Fraunhofer |
| R4-2105796 | WF on timing requirements for NR NTN | Xiaomi |
| R4-2105822 | Email discussion summary: [98-bis-e][222] NR_NTN_solutions_RRM_1 | Moderator (Fraunhofer HHI) |
| R4-2107277 | NTN UL timing accuracy | THALES |
| 8.8.4.1 | General | |
| R4-2104603 | Discussion on general NTN RRM related issues | CMCC |
| R4-2104763 | Discussion on RRM requirements for NTN | CATT |
| R4-2104764 | draft LS reply on NTN UL time and frequency synchronization requirements | CATT |
| R4-2105142 | Discussion on NTN GNSS requirement | LG Electronics UK |
| R4-2105692 | Email discussion summary for [98-bis-e][222] NR_NTN_solutions_RRM_1 | Moderator (Fraunhofer HHI) |
| R4-2107030 | Discussion on general issues for NTN RRM | Huawei, HiSilicon |
| R4-2107254 | NTN - On reference points | Nokia, Nokia Shanghai Bell |
| 8.8.4.2 | Timing requirements | |
| R4-2104604 | Discussion on NTN timing requirements | CMCC |
| R4-2104689 | Discussion on timing requirements for NR NTN | Xiaomi |
| R4-2104765 | Discussion on timing requirements for NTN | CATT |
| R4-2104927 | Discussion on timing requirements for NTN | ZTE Corporation |
| R4-2104985 | Discussion on RRM timing related requirements for NTN | NEC |
| R4-2105139 | Timing requirements | Ericsson |
| R4-2105140 | Reply LS to RAN1: LS on NTN UL time and frequency synchronization requirements (Timing) | Ericsson |
| R4-2105693 | Email discussion summary for [98-bis-e][223] NR_NTN_solutions_RRM_2 | Moderator (Xiaomi) |
| R4-2105823 | Email discussion summary for [98-bis-e][223] NR_NTN_solutions_RRM_2 | Moderator (Xiaomi) |
| R4-2106360 | Discussion on timing requirements in NTN | MediaTek inc. |
| R4-2106444 | Discussion on NTN timing pre-compensation | Intel Corporation |
| R4-2106947 | Discussion on NTN timing related requirements | Huawei, HiSilicon |
| R4-2107259 | NTN - On timing requirements | Nokia, Nokia Shanghai Bell |
| R4-2107291 | Timing requirements in NTN Systems | Qualcomm Incorporated |
| 8.8.4.3 | Measurement requirements | |
| R4-2104598 | NTN RRM measurement requirements | CMCC |
| R4-2104690 | Discussion on measurement requirements for NR NTN | Xiaomi |
| R4-2104766 | Discussion on measurement requirements for NTN | CATT |
| R4-2104816 | Measurement RRM requirements for NTN | Ericsson |
| R4-2104834 | On GNSS measurement for NTN | Apple |
| R4-2104986 | Discussion on RRM measurement requirements for NTN | NEC |
| R4-2105143 | Discussion on measurement requirements for NTN | LG Electronics UK |
| R4-2106939 | Discussion on measurement in NTN | Huawei, HiSilicon |
| R4-2107256 | NTN - On measurement requirements | Nokia, Nokia Shanghai Bell |
| R4-2107292 | Measurement requirements in NTN Systems | Qualcomm Incorporated |
| 8.9 | UE Power Saving Enhancements | |
| R4-2105694 | Email discussion summary for [98-bis-e][224] NR_UE_pow_sav_enh | Moderator (MediaTek inc.) |
| 8.9.1 | General and work plan | |
| R4-2105824 | Email discussion summary: [98-bis-e][224] NR_UE_pow_sav_enh_RRM | Moderator (MediaTek) |
| R4-2107082 | Considerations on study phase conclusions for R17 RLM BFD relaxation | vivo |
| 8.9.2 | UE measurements relaxation for RLM and/or BFD | |
| R4-2104605 | Discussion on RLM/BFD relaxation for NR power saving enhancement | CMCC |
| R4-2104693 | Discussion on RLM/BFD measurement relaxation for power saving | Xiaomi |
| R4-2104756 | Discussion on RLM/BFD relaxation measurement | CATT |
| R4-2104757 | Update simulation results for RLM/BFD relaxation | CATT |
| R4-2104850 | UE measurements relaxation for RLM and/or BFD | Apple |
| R4-2104908 | Power saving RRM discussion | Qualcomm, Inc. |
| R4-2105797 | WF on RLM/BM relaxation for NR UE Power saving | MediaTek |
| R4-2106461 | Discussions on UE power saving for RLM and BM | Intel Corporation |
| R4-2106539 | Discussion on RRM requirements for R17 RLM/BFD relaxation | OPPO |
| R4-2106540 | Simulation results for R17 RLM/BFD relaxation | OPPO |
| R4-2106581 | Simulation results for RLM/BFD measurement relaxation | Nokia, Nokia Shanghai Bell |
| R4-2106582 | Discussion about RLM/BFD measurement relaxation | Nokia, Nokia Shanghai Bell |
| R4-2106851 | Simulation results on UE power saving for RLM and BM | Ericsson |
| R4-2106852 | Discussions on UE power saving for RLM and BM | Ericsson |
| R4-2106915 | On RLM and RLF relaxation for UE power saving | ZTE Corporation |
| R4-2106942 | Discussion on RLM/BFD measurement relaxation for power saving enhancements | Huawei, HiSilicon |
| R4-2106943 | Updated simulation results for RLM/BFD relaxation evaluation | Huawei, HiSilicon |
| R4-2107083 | Discussion on R17 RLM and BFD relaxation for NR | vivo |
| R4-2107084 | Evaluation results on R17 RLM and BFD relaxation for NR | vivo |
| R4-2107085 | Updated evaluation assumptions for R17 RLM and BFD relaxation | vivo |
| R4-2107124 | Evaluation on Rel-17 RLM/BFD measurement relaxation | MediaTek inc. |
| 8.10.1 | General and work plan | |
| R4-2104528 | General discussions on operating bands for SL transmission | vivo |
| R4-2104533 | TP for SL enhancements | vivo |
| R4-2104969 | TR38.xxx v0.1.0 TR Update for SL enhancement in Rel-17 | LG Electronics France |
| R4-2105207 | Email discussion summary for [98-bis-e][134] NRSL_enh_Part_1 | Moderator (LG Electronics) |
| R4-2105400 | Way forward on general principle for SL enhancements | LG Electronics |
| R4-2105471 | Email discussion summary for [98-bis-e][134] NRSL_enh_Part_1 | Moderator (LG Electronics) |
| R4-2106676 | Discussion on Rel-16 NR V2X AMPR value for both NS_33 and NS_52 | Huawei, HiSilicon |
| 8.10.3 | System parameters (numerologies, rasters, CBW, etc) | |
| R4-2104529 | Discussion on system parameters for newly introduced SL bands | vivo |
| R4-2104775 | TP on CBW and system parameters for newly introduced SL bands | CATT |
| R4-2105401 | TP on CBW and system parameters for newly introduced SL bands | CATT |
| R4-2107305 | On CBW for licensed band supporting NR V2X | Huawei, HiSilicon |
| 8.10.4 | UE RF requirements for NR SL enhancement | |
| R4-2104971 | TP on operating scenarios for NR SL enhancements in Rel-17 | LG Electronics France |
| R4-2105402 | TP on operating scenarios for NR SL enhancements in Rel-17 | LG Electronics Franc |
| R4-2106291 | CR for TS 38.101-3 switching period for V2X con-current operation | Xiaomi |
| R4-2106292 | CR for TS 38.101-3 switching period for V2X con-current operation | Xiaomi |
| R4-2106297 | on switching period | Xiaomi |
| 8.10.4.2 | RX requirements | |
| R4-2104776 | TP on UE Rx RF requirement for NR SL enhancement | CATT |
| 8.10.5 | Partially used SL operation with NR Uu operating bands | |
| R4-2104970 | RF requirements for partial used licensed band bewteen NR Uu and NR SL operation | LG Electronics France |
| R4-2104972 | TP on MPR/coexistence simulation assumptions for leftover issues | LG Electronics France |
| R4-2105208 | Email discussion summary for [98-bis-e][135] NRSL_enh_Part_2 | Moderator (CATT) |
| R4-2105326 | Email discussion summary for [98-bis-e][135] NRSL_enh_Part_2 | Moderator (CATT) |
| R4-2105403 | Way forward on operating scenarios for SL and Uu operated in the same licensed band | CATT |
| R4-2105404 | Way forward on synchronization issue for SL and Uu operated in the same licensed band | Huawei, HiSilicon |
| R4-2105405 | TP on MPR/coexistence simulation assumptions for leftover issues | LG Electronics France |
| R4-2105472 | Email discussion summary for [98-bis-e][135] NRSL_enh_Part_2 | Moderator (CATT) |
| R4-2106301 | MPR for NR V2X intra-band con-current operation with Uu | LG Electronics Polska |
| 8.10.5.1 | FDM operation | |
| R4-2104530 | Further discussion on operation mode and core requirements for licensed bands partially used for SL | vivo |
| R4-2104778 | Discussion on FDM operation between SL and Uu | CATT |
| R4-2106293 | on FDM operation for partially used SL operation | Xiaomi |
| R4-2106554 | R17 V2X FDM operation | OPPO |
| R4-2107241 | FDM operation for partially used SL operation in licensed band | Ericsson |
| R4-2107303 | On FDM operation for SL and Uu in licensed bands | Huawei, HiSilicon |
| 8.10.5.2 | TDM operation | |
| R4-2104777 | Discussion on TDM operation between SL and Uu | CATT |
| R4-2106298 | on TDM operation for partially used SL operation | Xiaomi |
| R4-2107304 | On TDM operation for SL and Uu in licensed bands | Huawei, HiSilicon |
| 8.10.5.3 | Synchronous operation between NR Uu and NR SL in a TDD band | |
| R4-2104779 | Discussion on synchronous operation between SL and Uu | CATT |
| R4-2104919 | Synchronization and timing reference for NR SL and general issues on SL enhancements | Qualcomm Incorporated |
| R4-2106299 | synchronous operation between NR Uu and NR SL in an operating band | Xiaomi |
| R4-2106555 | R17 V2X synchronization | OPPO |
| R4-2107243 | SL UE synchronization issue for licensed operation | Ericsson |
| R4-2107302 | On synchronous operation between Uu and SL | Huawei, HiSilicon |
| 8.10.5.4 | Others | |
| R4-2104780 | LS on synchronous operation between Uu and SL in licensed band | CATT |
| R4-2105406 | LS on synchronous operation between Uu and SL in licensed band | CATT |
| 8.10.6 | High power UE(PC2) for SL | |
| R4-2105209 | Email discussion summary for [98-bis-e][136] NRSL_enh_Part_3 | Moderator (Huawei, HiSilicon) |
| R4-2105329 | Email discussion summary for [98-bis-e][136] NRSL_enh_Part_3 | Moderator (Huawei) |
| R4-2105407 | Way forward on PC2 NR V2X | Huawei, HiSilicon |
| R4-2105473 | Email discussion summary for [98-bis-e][136] NRSL_enh_Part_3 | Moderator (Huawei) |
| 8.10.6.1 | TX requirements | |
| R4-2104531 | Further discussion on HPUE for SL enhancements | vivo |
| R4-2105000 | NR V2X PC2 UE MPR and A-MPR simulation results for PSCCH/PSSCH in n47 | LG Electronics Inc. |
| R4-2106295 | on HPUE for V2X RF requirements | Xiaomi |
| R4-2106673 | Discussion on n47 PC2 MPR simulation results | Huawei, HiSilicon |
| 8.10.6.2 | Coexistence study | |
| R4-2104532 | Initial results for coexistence evaluation in n38 | vivo |
| R4-2105408 | Initial results for coexistence evaluation in n38 | vivo |
| R4-2106675 | Discussion on the SL adjacent coexistence simulation results for PC2 | Huawei, HiSilicon |
| 8.10.6.3 | Others | |
| R4-2106296 | on HPUE signalling issue | Xiaomi |
| R4-2106674 | Discussion on n47 PC2 AMPR simulation results | Huawei, HiSilicon |
| R4-2107242 | On PC2 power class V2X UE | Ericsson |
| 8.11.1 | General and work plan | |
| R4-2105981 | Email discussion summary for [98-bis-e][ 310] NR_Repeater_General | Moderator (Qualcomm) |
| R4-2105982 | Email discussion summary for [98-bis-e][311] NR_Repeater_RF | Moderator (CMCC) |
| R4-2106108 | WF on General issues for repeaters | Qualcomm |
| R4-2106109 | WF on Repeater Classes and Types | CMCC |
| R4-2106110 | WF on TDD Repeaters | Ericsson |
| R4-2106112 | WF on RF requirements for NR repeater | CMCC |
| R4-2106150 | Email discussion summary for [98-bis-e][310] NR_Repeater_General | Moderator (Qualcomm) |
| R4-2106151 | Email discussion summary for [98-bis-e][310] NR_Repeater_RF | Moderator (CMCC) |
| 8.11.1.1 | System parameters | |
| R4-2104614 | discussion on system parameters for NR repeater | CMCC |
| R4-2104667 | Bandwidth definitions and system parameters for repeaters | Ericsson |
| R4-2106323 | System parameters for NR repeaters | Nokia, Nokia Shanghai Bell |
| R4-2106348 | Views on NR repeater multi-band supporting | NTT DOCOMO, INC. |
| 8.11.1.2 | Repeater Class/Type | |
| R4-2104611 | discussion on repeater class | CMCC |
| R4-2104668 | Repeaters and classes | Ericsson |
| R4-2104793 | Discussion on repeater class and type | CATT |
| R4-2104987 | Discussion on NR repeater deployment scenario and repeater class | NEC |
| R4-2106324 | Identifying classes/types for NR-Repeaters | Nokia, Nokia Shanghai Bell |
| 8.11.1.3 | TDD repeater synchronization assumption | |
| R4-2104616 | Discussion on TDD synchronization related requirements for repeater | CMCC |
| R4-2104676 | Repeaters TDD requirements | Ericsson |
| R4-2104700 | Considerations on TDD repeater synchronization assumption | Sony |
| R4-2104704 | Repeaters in TDD | Qualcomm Incorporated |
| R4-2104794 | Discussion on TDD repeater related requirements | CATT |
| R4-2106325 | TDD repeater synchronization assumptions | Nokia, Nokia Shanghai Bell |
| R4-2106349 | Views on TDD repeater synchronization assumption | NTT DOCOMO, INC. |
| R4-2106603 | Discussion on sync issues for TDD repeater | ZTE Corporation |
| R4-2107107 | Discussion on TDD synchronisation | Huawei |
| 8.11.1.4 | Others | |
| R4-2104596 | Discussion on NR repeater core specification structure | CMCC |
| R4-2104597 | Skeleton TS 38.106 NR Repeater radio transmission and reception v0.0.1 | CMCC |
| R4-2104615 | Discussion on signal quality related requirements for NR repeater | CMCC |
| R4-2104673 | On OTA and test issues | Ericsson |
| R4-2106111 | NR repeater modified work plan | Qualcomm |
| R4-2106326 | NR repeater deployment/implementation related issues | Nokia, Nokia Shanghai Bell |
| R4-2106920 | Configurable Bandwidths for Repeaters | Qualcomm Incorporated |
| R4-2107212 | NR repeater modified work plan | Qualcomm Incorporated |
| R4-2107213 | NR repeater TS skeleton | Qualcomm Incorporated |
| 8.11.2 | Conductive RF core requirements | |
| R4-2107106 | Discussion on RF paramters to be specified | Huawei |
| 8.11.2.1 | Transmitted power related requirements | |
| R4-2104612 | Discussion on transmitter power related conducted requirements | CMCC |
| R4-2104671 | Conducted TX power requirements for repeaters | Ericsson |
| R4-2104795 | Discussion on NR repeater conducted output power | CATT |
| R4-2104988 | Discussion on NR repeater FR1 maximum output power and ALC/AGC | NEC |
| R4-2106327 | Conducted power related requirements consideration for NR-Repeaters | Nokia, Nokia Shanghai Bell |
| R4-2106350 | Views on transmitted power related requirements for FR1 NR repeater | NTT DOCOMO, INC. |
| 8.11.2.2 | Emission requirements | |
| R4-2104617 | Discussion on emission related conducted requirements | CMCC |
| R4-2104669 | Conducted unwanted emissions requirements for repeaters | Ericsson |
| R4-2104796 | Discussion on NR repeater conducted emission requirement | CATT |
| R4-2106328 | Conductive emission requirement consideration for NR-Repeaters | Nokia, Nokia Shanghai Bell |
| R4-2106351 | Views on emission requirements for FR1 NR repeater | NTT DOCOMO, INC. |
| 8.11.2.3 | Others | |
| R4-2104670 | NR repeaters conducted other requirements | Ericsson |
| R4-2104797 | Discussion on NR repeater conducted other requirements | CATT |
| R4-2106329 | Repeater timing | Nokia, Nokia Shanghai Bell |
| 8.11.3.1 | Transmitted power related requirements | |
| R4-2104613 | Discussion on transmitter power related FR2 radiated requirements | CMCC |
| R4-2104674 | Radiated TX power for repeaters | Ericsson |
| R4-2104798 | Discussion on power requirement for FR2 NR repeater | CATT |
| R4-2106330 | Radiated power related requirements consideration for NR-Repeaters | Nokia, Nokia Shanghai Bell |
| R4-2106352 | Views on transmitted power related requirements for FR2 NR repeater | NTT DOCOMO, INC. |
| 8.11.3.2 | Emission requirements | |
| R4-2104618 | Discussion on transmitter emission related radiated requirements | CMCC |
| R4-2104672 | Radiated emissions requirements | Ericsson |
| R4-2104799 | Discussion on emission requirements for FR2 NR repeater | CATT |
| R4-2106331 | Radiated emission requirement consideration for NR-Repeaters | Nokia, Nokia Shanghai Bell |
| R4-2106353 | Views on emission requirements for FR2 NR repeater | NTT DOCOMO, INC. |
| 8.11.3.3 | Others | |
| R4-2104675 | Other radiated repeater requirements | Ericsson |
| R4-2104800 | Discussion on other requirements for FR2 NR repeater | CATT |
| R4-2106332 | Frequency error considerations for FR2 NR-Repeaters | Nokia, Nokia Shanghai Bell |
| 8.11.4 | EMC core requirements | |
| R4-2104961 | Skeleton TS 38.114V0.0.1“NR; Repeaters ElectroMagnetic Compatibility (EMC)” | ZTE Corporation |
| R4-2106087 | WF on NR repeaters EMC requirements | ZTE Corporation |
| R4-2106514 | Discussion on EMC requirements for NR Repeater | Ericsson |
| R4-2107252 | Discussion on NR repeater EMC | Nokia, Nokia Shanghai Bell |
| 8.12 | Extending current NR operation to 71GHz | |
| R4-2105414 | LS out on 60GHz beam switching | Apple |
| 8.12.1 | General and work plan | |
| R4-2104535 | Further discussion on the minimum and maximum channel bandwidths for B52.6G | vivo |
| R4-2104537 | Draft Reply LS on bandwidth and channelization | vivo |
| R4-2104806 | Discussion on the co-exit simulation assumption | CATT |
| R4-2104895 | Testability aspects for the 52.6 GHz to 71 GHz frequency range | Apple |
| R4-2105210 | Email discussion summary for [98-bis-e][137] NR_ext_to_71GHz_Part_1_NWM | Moderator (Intel) |
| R4-2105328 | [98-bis-e][137] NR_ext_to_71GHz_Part_1_NWM - Version 0.0.3 RAN4 | Moderator (Intel) |
| R4-2105411 | Reply LS to RAN1 on max/min CBW and channelization for NR operation in 52.6 - 71 GHz | Intel |
| R4-2105412 | NR 52.6 - 71 GHz work plan | Intel |
| R4-2105474 | Email discussion summary for [98-bis-e][137] NR_ext_to_71GHz_Part_1_NWM | Moderator (Intel) |
| R4-2106300 | work plan of extending NR to 71GHz | Xiaomi |
| R4-2106464 | NR 52.6 - 71 GHz work plan | Intel Corporation |
| R4-2106665 | Work plan considerations for NR extension to 71 GHz | Nokia, Nokia Shanghai Bell |
| R4-2106692 | On 52.6 to 71 GHz minimum/maximum channel bandwidth, draft LS to RAN1 | Ericsson |
| R4-2107210 | 60 GHz UE switching times | Qualcomm Incorporated |
| 8.12.2 | Band plans and regulatory requirements | |
| R4-2104534 | Discussion on band plan for B52.6GHz | vivo |
| R4-2104802 | Discussion on the band plan of 52.6-71 GHz | CATT |
| R4-2104885 | Regulatory status for the frequency range 52.6 GHz to 71 GHz and potential band plan | Apple |
| R4-2105410 | Way forward on WF on [137] NR_ext_to_71GHz_Part1 | Intel |
| R4-2106465 | On spectrum situation and band plan for 52.6 - 71 GHz | Intel Corporation |
| R4-2106587 | Discussion on band plan for 52.6-71GHz | ZTE Corporation |
| R4-2107076 | bandplan for 52-71GHz frequency range | Ericsson |
| R4-2107189 | Bandplan for a NR band in the range 52.6GHz – 71GHz | Nokia, Nokia Shanghai Bell |
| 8.12.3 | System parameters (numerologies, rasters, CBW, etc) | |
| R4-2104536 | General discussion on channel raster and sync raster for B52.6G | vivo |
| R4-2104594 | Discussion on system parameters for NR in 52.6GHz ~ 71GHz | CMCC |
| R4-2104804 | Discussion on the reply LS on the CBW and channelization | CATT |
| R4-2104805 | Discussion on the reply LS on beam switching gap | CATT |
| R4-2104821 | Discussion on system parameters for NR operation in 52.6GHz - 71GHz | Apple |
| R4-2106305 | Discussion on minimum and maximum bandwidth for NR 52.6 to 71 GHz | LG Electronics Finland |
| R4-2106466 | On system parameters for NR 52.6 - 71 GHz | Intel Corporation |
| R4-2106588 | Discussion on system parameters for 52.6-71GHz | ZTE Corporation |
| R4-2106691 | 52.6-71 GHz system parameters | Ericsson |
| R4-2107190 | System parameters for a NR band in the range 52.6GHz – 71GHz | Nokia, Nokia Shanghai Bell |
| R4-2107286 | on channel bandwidth for >52.6GHz Band | HiSilicon Technologies Co. Ltd |
| 8.12.4 | UE RF requirements | |
| R4-2105211 | Email discussion summary for [98-bis-e][138] NR_ext_to_71GHz_Part_2 | Moderator (Qualcomm) |
| R4-2105413 | Way forward on 60GHz beam switching | Apple |
| R4-2105415 | Way forward on system simulations for 60 GHz | Qualcomm |
| R4-2105475 | Email discussion summary for [98-bis-e][138] NR_ext_to_71GHz_Part_2 | Moderator (Qualcomm |
| R4-2105496 | Email discussion summary for [98-bis-e][138] NR_ext_to_71GHz_Part_2 | Moderator (Qualcomm) |
| R4-2107271 | On beam switching for 60GHz Band | HiSilicon Technologies Co. Ltd |
| 8.12.4.1 | TX requirements | |
| R4-2105090 | On UE TX requirements for operations up to 71 GHz | Ericsson |
| R4-2106909 | On open loop TPC and transient requirements for NR in the 52.6 - 71 GHz frequency range | Apple |
| R4-2107191 | On UE Tx RF aspects for a NR band in the range 52.6GHz – 71GHz | Nokia, Nokia Shanghai Bell |
| R4-2107211 | 60 GHz UE TX EVM | Qualcomm Incorporated |
| R4-2107342 | UE Tx requirements for NR extension to 71GHz | Intel Corporation |
| 8.12.4.2 | RX requirements | |
| R4-2107192 | On UE Rx RF aspects for a NR band in the range 52.6GHz – 71GHz | Nokia, Nokia Shanghai Bell |
| R4-2107343 | UE Rx requirements for NR extension to 71GHz | Intel Corporation |
| 8.12.5 | BS RF requirements | |
| R4-2105983 | Email discussion summary for [98-bis-e][312] NR_exto71GHz_BSRF | Moderator (Nokia) |
| R4-2106113 | WF on BS RF TX requirements for 52.6 – 71 GHz | Nokia |
| R4-2106114 | WF on BS RF RX requirements for 52.6 – 71 GHz | Ericsson |
| R4-2106152 | Email discussion summary for [98-bis-e][312] NR_exto71GHz_BSRF | Moderator (Nokia) |
| 8.12.5.1 | TX requirements | |
| R4-2104456 | Proposals on BS transmitter requirements for extending current NR operation to 71 GHz | Nokia, Nokia Shanghai Bell |
| R4-2104731 | Discussion on BS TX RF requirements for 52.6-71GHz | CATT |
| R4-2106355 | On BS transmitter aspects extending NR to 71 GHz | Ericsson |
| R4-2106589 | Discussion on BS Tx requirements for 52.6-71GHz | ZTE Corporation |
| 8.12.5.2 | RX requirements | |
| R4-2104457 | Proposals on BS receiver requirements for extending current NR operation to 71 GHz | Nokia, Nokia Shanghai Bell |
| R4-2104683 | On BS receiver requirements for 52-71 GHz | Ericsson |
| R4-2104732 | Discussion on BS RX RF requirements for 52.6-71GHz | CATT |
| R4-2106590 | Discussion on BS Rx requirements for 52.6-71GHz | ZTE Corporation |
| 8.12.6 | Others | |
| R4-2104439 | Simulation results for NR coexistence study indoor deployment at 60GHz | Qualcomm CDMA Technologies |
| R4-2104441 | Simulation results for NR coexistence study: dense urban micro deployment at 60GHz | Qualcomm CDMA Technologies |
| R4-2104588 | On extension of FR2 or new Frequency Range (FR3) to introduce 52.6-71 GHz | Ericsson France S.A.S |
| R4-2104595 | Discussion on frequency range terminology for 52.6GHz ~ 71GHz | CMCC |
| R4-2104803 | Discussion on the frequency range of 52.6-71 GHz | CATT |
| R4-2104835 | On frequency range definition between 52.6GHz and 71GHz | Apple |
| R4-2105138 | Reply LS to RAN1: LS on beam switching gap for 60 GHz band | Ericsson |
| R4-2105172 | Simulation results for NR coexistence study indoor deployment at 60GHz | Qualcomm CDMA Technologies |
| R4-2105173 | Simulation results for NR coexistence study: dense urban micro deployment at 60GHz | Qualcomm CDMA Technologies |
| R4-2106294 | on frequency range definition for NR 52_71GHz | Xiaomi |
| R4-2106467 | On frequency range definition on 52.6 - 71 GHz | Intel Corporation |
| R4-2106591 | Discussion on switching delay for 52.6-71GHz | ZTE Corporation |
| R4-2106592 | Discussion on frequency range definition for 52.6-71GHz | ZTE Corporation |
| R4-2106666 | On frequency range definition for 52.6 – 71 GHz | Nokia, Nokia Shanghai Bell |
| R4-2107316 | Discussion on frequency range definition for 52-71GHz | Skyworks Solutions Inc. |
| 8.13 | Enhancements to Integrated Access and Backhaul (IAB) for NR | |
| R4-2105984 | Email discussion summary for [98-bis-e][313] NR_eIAB | Moderator (Samsung) |
| 8.13.1 | General and work plan | |
| R4-2105039 | Rel-17 IAB: updated work plan | Samsung, Qualcomm |
| R4-2105040 | Overview on NR Rel-17 eIAB | Samsung |
| R4-2106115 | WF on Rel-17 eIAB RAN4 scope | Samsung |
| R4-2106153 | Email discussion summary for [98-bis-e][313] NR_eIAB | Moderator (Samsung) |
| R4-2106662 | IAB Rel.17 – General considerations | Nokia, Nokia Shanghai Bell |
| R4-2107239 | RF impact analysis for IAB R17 scope | Ericsson |
| 8.13.2 | RF requirements | |
| R4-2106663 | IAB Rel.17 – RF requirements | Nokia, Nokia Shanghai Bell |
| R4-2107240 | IAB MT /DU case 6/7 timing | Ericsson |
| 8.13.3 | Others | |
| R4-2106664 | IAB Rel.17 – CLI in FDM and SDM operation | Nokia, Nokia Shanghai Bell |
| 8.14.1 | General and work plan | |
| R4-2104951 | Work plan for Further enhancement on NR demodulation performance WI | China Telecom |
| R4-2104952 | TR skeleton (V0.0.1) for Inter-user interference suppression for NR Multiple-User Multiple-Input Multiple-Output (MU-MIMO) | China Telecom |
| R4-2105994 | Email discussion summary for [98-bis-e][323] NR_perf_enh2_Demod_Part1 | Moderator (China Telecom) |
| R4-2106116 | WF on general and PDSCH demodulation requirements for inter-cell interference MMSE-IRC | Intel Corporation |
| R4-2106117 | WF on CQI reporting requirements for inter-cell interference MMSE-IRC | Ericsson |
| R4-2106118 | WF on MMSE-IRC receiver for intra-cell inter-user interference | Huawei |
| R4-2106119 | Work plan for Further enhancement on NR demodulation performance WI | China Telecom |
| R4-2106154 | Email discussion summary for [98-bis-e][323] NR_perf_enh2_Demod_Part1 | Moderator (China Telecomm |
| R4-2106155 | Email discussion summary for [98-bis-e][324] NR_perf_enh2_Demod_Part2_NWM | Moderator (Huawei |
| 8.14.2.1 | MMSE-IRC receiver for inter-cell interference | |
| R4-2104606 | Discussion on demodulation enhancement for inter-cell interference suppressing | CMCC |
| R4-2104846 | On PDSCH requirements in intercell interference scenarios | Apple |
| R4-2104953 | On UE MMSE-IRC receiver for inter-cell interference suppression | China Telecom |
| R4-2104977 | Views on MMSE-IRC receiver for inter-cell interference test | NTT DOCOMO, INC. |
| R4-2106426 | Discussion on MMSE-IRC requirements for scenario with inter-cell interference | Intel Corporation |
| R4-2106833 | Discsussion on MMSE-IRC receiver for inter-cell interference | Huawei, HiSilicon |
| R4-2106867 | Discussion on MMSE-IRC receiver for inter-cell interference | Ericsson |
| R4-2107093 | Views on MMSE-IRC receiver for inter-cell interference | MediaTek inc. |
| 8.14.2.2 | MMSE-IRC receiver for intra-cell inter-user interference | |
| R4-2104607 | Discussion on NR demodulation enhancement for intra-cell inter-user interference suppressing | CMCC |
| R4-2104847 | On PDSCH requirements in MU-MIMO scenarios | Apple |
| R4-2104954 | On UE MMSE-IRC receiver for intra-cell inter-user interference suppression | China Telecom |
| R4-2106427 | Discussion on MMSE-IRC requirements for scenario with intra-cell inter-user interference | Intel Corporation |
| R4-2106834 | Discussion on MMSE-IRC receiver for intra-cell inter-user interference | Huawei, HiSilicon |
| R4-2106868 | Disucsson on MMSE-IRC receiver for intra-cell inter-user interference | Ericsson |
| 8.14.3.1 | PUSCH demodulation requirements for FR1 256QAM | |
| R4-2104483 | Views on PUSCH FR1 256QAM demodulation requirements | China Telecommunications |
| R4-2104557 | Discussion on FR1 PUSCH 256QAM demodulation requirement | Ericsson |
| R4-2104608 | Discussion on BS demodulation enhancement for FR1 256QAM | CMCC |
| R4-2104730 | Discussion on PUSCH demodulation requirements for FR1 256QAM | CATT |
| R4-2105031 | View on PUSCH demodulation requirement with FR1 256QAM | Samsung |
| R4-2105995 | Email discussion summary for [98-bis-e][324] NR_perf_enh2_Demod_Part2_NWM | Moderator (Huawei, HiSilicon) |
| R4-2106347 | Views on FR1 PUSCH 256QAM | NTT DOCOMO, INC. |
| R4-2106428 | Discussion on PUSCH requirements for FR1 256QAM | Intel Corporation |
| R4-2106782 | On PUSCH demodulation requirements for FR1 256QAM | Nokia, Nokia Shanghai Bell |
| R4-2106835 | Discussion on PUSCH demodulation requirements for FR1 256QAM | Huawei, HiSilicon |
| 8.15.1 | General and work plan | |
| R4-2104726 | Link level simulation results for 1024QAM for NR FR1 | CATT |
| R4-2104727 | System level simulation results for 1024QAM for NR FR1 | CATT |
| R4-2105212 | Email discussion summary for [98-bis-e][139] NR_DL1024QAM_FR1 | Moderator (Ericsson) |
| R4-2105416 | Way forward on UE RF requirements for DL1024QAM | Ericsson |
| R4-2105476 | Email discussion summary for [98-bis-e][139] NR_DL1024QAM_FR1 | Source: Moderator (Ericsson) |
| R4-2106121 | WF on BS RF requirements for 1024QAM | Ericsson |
| R4-2106156 | Email discussion summary for [98-bis-e][314] NR_DL1024QAM_BSRF | Moderator (Ericsson) |
| R4-2106487 | Scenarios for support of 1024QAM | Huawei, HiSilicon, CMCC, China Unicom |
| R4-2106858 | Work plan for DL 1024QAM for NR FR1 | Ericsson, Nokia, Nokia Shanghai Bell |
| 8.15.2 | BS TX RF requirements | |
| R4-2104728 | Discussion on BS TX RF requirements for 1024QAM for NR FR1 | CATT |
| R4-2104989 | Discussion on BS TX RF requirements for NR FR1 DL 1024QAM | NEC |
| R4-2105985 | Email discussion summary for [98-bis-e][314] NR_DL1024QAM_BSRF | Moderator (Ericsson) |
| R4-2106309 | Considerations on BS RF transmitter requirements for 1024QAM for FR1 | Nokia, Nokia Shanghai Bell |
| R4-2106475 | BS test requirements for 1024QAM for NR FR1 | CATT |
| R4-2106488 | BS RF requirements for support of 1024QAM | Huawei, HiSilicon, CMCC, China Unicom |
| R4-2106594 | Discussion on BS requirements for 1024QAM | ZTE Corporation |
| R4-2106687 | BS Requirement Overview and Impact for 1024 QAM | Ericsson |
| 8.15.3 | UE RX RF requirements | |
| R4-2104729 | Discussion on UE RX RF requirements for 1024QAM for NR FR1 | CATT |
| R4-2106489 | RX EVM for support of 1024QAM | Huawei, HiSilicon, CMCC, China Unicom |
| R4-2106688 | UE Requirement Overview and Impact for 1024 QAM | Ericsson |
| 8.16 | NR coverage enhancements | |
| R4-2105213 | Email discussion summary for [98-bis-e][140] NR_cov_enh | Moderator (Huawei, HiSilicon) |
| 8.16.1 | Phase continuity and power consistency for PUSCH and PUCCH repetition | |
| R4-2104580 | Discussion on phase continuity and power consistency for UL repetition | MediaTek inc. |
| R4-2104955 | On non-zero gap between adjacent transmissions for PUCCH and PUSCH repetition | China Telecom |
| R4-2105417 | Reply LS on PUCCH and PUSCH repetition | Qualcomm |
| R4-2105418 | Way forward on phase continuity and power consistency for PUCCH and PUSCH repetition | Huawei, HiSilicon |
| R4-2105477 | Email discussion summary for [98-bis-e][140] NR_cov_enh | Moderator (Huawei) |
| R4-2106918 | Discussion on phase continuity for PUSCH and PUCCH repetitions | InterDigital Communications |
| R4-2107273 | on phase continuty for multiple transmissions | HiSilicon Technologies Co. Ltd |
| R4-2107284 | Phase continuity over the gap in tx | Qualcomm Incorporated |
| R4-2107366 | Phase continuity over the gap in tx | Qualcomm Incorporated |
| 9.1.1 | General | |
| R4-2104523 | TP to TR38.884 v0.2.0 on MU Annex | vivo |
| R4-2104897 | Rapporteur input to TR38.884 | Apple, vivo |
| R4-2104898 | TR38.884 work split | Apple, vivo |
| R4-2105998 | Email discussion summary for [98-bis-e][327] FR2_enhTestMethods | Moderator (Apple) |
| R4-2106127 | WF on agreements and remaining issues with FR2 test method enhancements | Apple |
| R4-2106157 | Email discussion summary for [98-bis-e][327] FR2_enhTestMethods | Moderator (Apple) |
| R4-2106162 | LS on band-dependent parameters for the FR2 demodulation setup | Apple |
| R4-2106165 | Draft TR38.884 Study on enhanced test methods for FR2 NR UEs v0.3.0 | Apple,vivo |
| 9.1.2 | Test methodology for high DL power and low UL power test cases | |
| R4-2104522 | Discussions on test procedure of FR2 enhanced test methods | vivo |
| R4-2104684 | On black box test | Huawei Tech.(UK) Co.. Ltd |
| R4-2106130 | On CFFNF and CFFDNF test methodologies for high DL power and low UL power test cases | Keysight Technologies UK Ltd |
| R4-2106695 | DNF Method – EIRP and TRP accuracy | MVG Industries, Sony |
| R4-2107130 | On CFFNF and CFFDNF test methodologies for high DL power and low UL power test cases | Keysight Technologies UK Ltd |
| R4-2107187 | Analysis of NF based solutions | ROHDE & SCHWARZ |
| 9.1.3 | Polarization basis mismatch | |
| R4-2104489 | Transmit signal quality measurements by TE with dual pol Rx | Qualcomm Incorporated |
| R4-2104558 | TPMI, 2-port CSI-RS, and EVM issues about polarization basis mismatch | MediaTek Beijing Inc. |
| R4-2104569 | Considerations on test with TPMI method | Anritsu Corporation |
| R4-2104701 | Views on solutions to minimize the impact of polarization basis mismatch | Sony, Ericsson |
| R4-2105043 | Discussion on TPMI configuration in EIRP measurement | Samsung |
| R4-2106570 | Solution to minimize the impact of polarization basis mismatch | OPPO |
| R4-2107111 | Text proposal to TR38.884: FR2 UL EVM measurements | Rohde & Schwarz |
| 9.1.4 | Enhanced test methods for inter-band (FR2+FR2) CA | |
| R4-2104958 | TP to TR 38.884 on Inter-band DL CA in FR2 | Anritsu Corporation |
| 9.1.5 | Extreme temperature conditions | |
| R4-2104521 | TP to TR38.884 v0.2.0 on ETC system | vivo |
| R4-2104570 | Considerations on ETC MUs and a testability | Anritsu Corporation |
| R4-2104571 | Comparison of path loss at frequency around band n262 | Anritsu Corporation |
| R4-2106129 | TP to TR38.884 v0.2.0 on ETC system | vivo |
| R4-2107128 | On extreme temperature condition testing | Keysight Technologies UK Ltd |
| 9.1.6 | Test time reduction | |
| R4-2104518 | LS on antenna assumption and measurement grids for FR2 PC3 | vivo |
| R4-2104519 | Discussion and TP to TR38.884 on FR2 testing time reduction | vivo |
| R4-2105001 | Discussion on enhanced test method to reduce FR2 OTA test time | LG Electronics Inc. |
| R4-2105044 | Discussion on prioritized methods for test time reduction | Samsung |
| R4-2106128 | LS on antenna assumption and measurement grids for FR2 PC3 | vivo |
| R4-2106164 | Text proposal to TR38.884: Fast Spherical Coverage Method | Rohde & Schwarz |
| R4-2107110 | Text proposal to TR38.884: Fast Spherical Coverage Method | Rohde & Schwarz |
| R4-2107129 | Draft LS to RAN5 on Test Time Reduction | Keysight Technologies UK Ltd |
| R4-2107296 | Discussion on enhance test method to reduce FR2 OTA test time | HiSilicon Technologies Co. Ltd |
| 9.1.7 | Extension of frequency applicability of permitted methods in 38.810 for band n262 | |
| R4-2104896 | On permitted test methods for demodulation in band n262 | Apple |
| 9.2 | Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | |
| R4-2105214 | Email discussion summary for [98-bis-e][141] FS_NR_eff_BW_util | Moderator (Ericsson) |
| R4-2105419 | Way forward on Evaluation of Irregular BW Approaches | Ericsson |
| R4-2105478 | Email discussion summary for [98-bis-e][141] FS_NR_eff_BW_uti | Moderator (Ericsson) |
| 9.2.1 | General and work plan | |
| R4-2105420 | TP to the TR 38.844: Terminology | Ericsson, Nokia, Nokia Shanghai Bell |
| R4-2106690 | TP to the TR 38.844: Terminology | Ericsson, Nokia, Nokia Shanghai Bell |
| 9.2.2 | Evaluation of use of larger channel bandwidths than operator licensed bandwidth | |
| R4-2104587 | Further input on the blanking approach for irregular BWs | Ericsson France S.A.S |
| R4-2104600 | Discussion on use of larger channel bandwidth | CMCC |
| R4-2104886 | Non-standard spectrum allocations for NR bands (larger channel) | Apple |
| R4-2106485 | Consideration on use of larger channel bandwidth | Huawei, HiSilicon |
| R4-2107253 | Support of irregular channel bandwidth with larger or overlapped BW | Skyworks Solutions Inc. |
| R4-2107328 | TP for TR 38.844: 6 MHz for n85 with larger CHBW | T-Mobile USA |
| 9.2.3 | Evaluation of use of overlapping UE channel bandwidths | |
| R4-2104599 | Discussion on overlapping channel bandwidths | CMCC |
| R4-2104707 | Handling of Channel Bandwidths That Are Not Multiples of 5MHz | Qualcomm Incorporated |
| R4-2104887 | Non-standard spectrum allocations for NR bands (overlapping channel) | Apple |
| R4-2106486 | Consideration for overlapping UE channel bandwidths | Huawei, HiSilicon |
| R4-2106689 | Overlapping UE Channel Bandwidth Approach | Ericsson |
| R4-2107040 | On the use of overlapping channel bandwidths from UE perspective | Nokia, Nokia Shanghai Bell |
| R4-2107319 | On SU for overlapping channel bandwidth | ZTE Wistron Telecom AB |
| R4-2107329 | TP for TR 38.844: 6 MHz for n85 with overlapping CHBW | T-Mobile USA |
| 9.3 | Study on extended 600MHz NR band | |
| R4-2105215 | Email discussion summary for [98-bis-e][142] FS_NR_600MHz_ext | Moderator (Ericsson) |
| R4-2105421 | Way forward on Coexistence with Other Services | Ericsson |
| R4-2105422 | Way forward on Frequency arrangements for further study and corresponding UE filter configurations | Qualcomm |
| R4-2105423 | Updated TR for extended 600MHz NR band | Spark |
| R4-2105479 | Email discussion summary for [98-bis-e][142] FS_NR_600MHz_ext | Moderator (Ericsson) |
| 9.3.3 | Coexistence study | |
| R4-2104717 | Coexistence for APT 600 MHz | Nokia, Nokia Shanghai Bell |
| R4-2104931 | Coexistence study for extended 600 MHz NR frequency band | ZTE Corporation |
| 9.3.4 | Study on frequency arrangements (such as options B1 and B2) | |
| R4-2104495 | Option B2 for Extended 600MHz NR band | Spark NZ Ltd |
| R4-2104718 | Frequency arrangements for APT 600 MHz | Nokia, Nokia Shanghai Bell |
| R4-2104817 | Discussion on Extended 600MHz Band Implementation Options | Skyworks Solutions Inc. |
| R4-2104891 | TP on band plan for 600 MHz | Apple |
| R4-2105094 | Further discussion on frequency arrangement for extended 600MHz NR Band | Xiaomi |
| R4-2106593 | Discussions on Option B1 and B2 for extended 600MHz | ZTE Corporation |
| R4-2106891 | Extended 600MHz band - Band and duplexer arrangement | Ericsson |
| R4-2107301 | Feasibility analysis of 600MHz duplexer | Huawei, HiSilicon |
| R4-2107348 | Filtering for extended 600 MHz band | Qualcomm Incorporated |
| 9.4 | Study on high power UE (power class 2) for one NR FDD band | |
| R4-2105216 | Email discussion summary for [98-bis-e][143] FS_NR_PC2_UE_FDD | Moderator (China Unicom |
| R4-2105424 | Way forward on PC2 for NR FDD band | China Unicom |
| R4-2105425 | Way forward on initial agreements on system performance evaluation | China Unicom |
| R4-2105480 | Email discussion summary for [98-bis-e][143] FS_NR_PC2_UE_FDD | Moderator (China Unicom) |
| R4-2105494 | Way forward on PC2 for NR FDD band | China Unicom |
| 9.4.1 | General | |
| R4-2104540 | Discussion on HPUE in NR FDD band | vivo |
| R4-2105497 | TR skeleton for Study on high power UE (power class 2) for one NR FDD band | China Unicom |
| R4-2106550 | Discussion on HP UE for FDD bands | Xiaomi |
| R4-2106912 | TR skeleton for Study on high power UE (power class 2) for one NR FDD band | China Unicom |
| 9.4.2 | Scheme(s) to comply with the SAR limits | |
| R4-2104509 | Clarification on testing assumptions of FDD-PC2 | SoftBank Corp. |
| R4-2106362 | Discussion on HPUE FDD band | ZTE Corporation |
| R4-2106560 | R17 FDD HPUE | OPPO |
| 9.4.3 | Interference issues | |
| R4-2104997 | Receiver sensitivity degradation for PC2 UE in FDD band | LG Electronics France |
| R4-2107298 | REFSENS analysis for FDD HPUE | Huawei, HiSilicon |
| 9.4.4 | UE implementation issues | |
| R4-2107299 | On feasibility of RF component to support FDD HPUE | Huawei, HiSilicon |
| R4-2107354 | UE related considerations for PC2 FDD | Qualcomm Incorporated |
| 9.4.5 | System performance evaluations | |
| R4-2104541 | Initial evaulation results of PC2 UE for NR FDD | vivo |
| R4-2104922 | System performance evaluation on FDD HPUE | ZTE Corporation |
| R4-2107119 | FDD PC2 system performance evaluations | Qualcomm Incorporated |
| R4-2107300 | System performance evaluation of FDD HPUE | Huawei, HiSilicon |
| 9.5 | Study on 5G NR UE Application Layer Data Throughput Performance | |
| R4-2105996 | Email discussion summary for [98-bis-e][325] NR_ATP | Moderator (Qualcomm Incorporated) |
| R4-2106158 | Email discussion summary for [98-bis-e][325] NR_ATP | Moderator (Qualcomm Incorporated) |
| 9.5.1 | General and work plan | |
| R4-2106122 | WF on 5G NR UE Application Layer Data Throughput Performance | Qualcomm |
| R4-2106124 | Work Plan for Study on 5G NR UE Application Layer Data Throughput Performance | Qualcomm Incorporated |
| R4-2107032 | Work Plan for Study on 5G NR UE Application Layer Data Throughput Performance | Qualcomm Incorporated |
| 9.5.2 | Test methodology | |
| R4-2106429 | Discussion on test methodology for NR UE Application Layer Data Throughput Performance requirements | Intel Corporation |
| R4-2106869 | Test methodology for application layer data throughput performance | Ericsson |
| R4-2107033 | Test Methodology for Application Layer Throughput Tests | Qualcomm Incorporated |
| 9.5.3 | Test parameters | |
| R4-2106430 | Discussion on test parameters for NR UE Application Layer Data Throughput Performance requirements | Intel Corporation |
| R4-2106870 | Test parameters for application layer performance | Ericsson |
| R4-2107035 | Test Parameters for Application Layer Throughput Tests | Qualcomm Incorporated |
| 9.6 | Study on band combination handling in RAN4 | |
| R4-2105217 | Email discussion summary for [98-bis-e][144] FS_BC_handling | Moderator (ZTE) |
| R4-2105426 | Way forward on Handling of SDL related EN-DC combinations | CHTTL |
| R4-2105427 | Way forward on Optimization to the tables of delta TIB and RIB | ZTE Corporation |
| R4-2105481 | Email discussion summary for [98-bis-e][144] FS_BC_handling | Moderator (ZTE) |
| 9.6.1 | General and TR | |
| R4-2104865 | On band combination handling | ZTE Corporation |
| R4-2104874 | TR skeleton 38.xxx v001 Band combination handling | ZTE Corporation |
| R4-2105431 | TR skeleton 38.xxx v001 Band combination handling | ZTE Corporation |
| 9.6.2 | How to introduce band combinations including TP format | |
| R4-2106683 | Discussion on Band combination handling | Huawei, HiSilicon |
| 9.6.3 | Rules and guidelines of specifying band combinations including notations of CA/DC combinations | |
| R4-2104864 | Further considerations on delta TIB and RIB simplification for band combinations | ZTE Corporation |
| R4-2104892 | TP on rules and guidelines for specifying band combinations | Apple |
| R4-2105430 | TP on rules and guidelines for specifying band combinations | Apple |
| R4-2107045 | Discussion on guidelines for handling SDL related EN-DC combinations | CHTTL |
| 9.6.4 | Improving RAN4 specification structures and reducing redundant contents | |
| R4-2104866 | CR to TS 38.101-1 on optimization to channel bandwidth per operating band (Rel-16) | ZTE Corporation |
| R4-2104867 | CR to TS 38.101-1 on optimization to channel bandwidth per operating band (Rel-17) | ZTE Corporation |
| R4-2104868 | CR to TS 38.101-2 on optimization to channel bandwidth per operating band (Rel-16) | ZTE Corporation |
| R4-2104869 | CR to TS 38.101-2 on optimization to channel bandwidth per operating band (Rel-17) | ZTE Corporation |
| R4-2104870 | CR to TS 38.104 on optimization to BS channel bandwidths and SCS per operating band (Rel-16) | ZTE Corporation |
| R4-2104871 | CR to TS 38.104 on optimization to BS channel bandwidths and SCS per operating band (Rel-17) | ZTE Corporation |
| R4-2104875 | draft CR to TS 38.101-1 on optimization to channel bandwidth per operating band (Rel-16) | ZTE Corporation |
| R4-2104876 | draft CR to TS 38.101-2 on optimization to channel bandwidth per operating band (Rel-16) | ZTE Corporation |
| R4-2104877 | draft CR to TS 38.104 on optimization to BS channel bandwidths and SCS per operating band (Rel-16) | ZTE Corporation |
| 10.1 | LTE inter-band Carrier Aggregation for 2 bands DL with 1 band UL | |
| R4-2105218 | Email discussion summary for [98-bis-e][145] LTE_Baskets | Moderator (Ericsson) |
| 10.1.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2107114 | Revised WID: Rel17 LTE inter-band CA for 2 bands DL with 1 band UL | Qualcomm Incorporated |
| R4-2107115 | TR 36.717-02-01 Rel-17 LTE inter-band CA for 2 bands DL and 1 band UL CA | Qualcomm Incorporated |
| 10.3.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2107036 | TR 36.717-04-01 v0.4.0 | Nokia, Nokia Shanghai Bell |
| 10.4.2 | UE RF with harmonic, close proximity and isolation issues | |
| R4-2104647 | TP for TR 36.717-02-02 to add UL configuration CA_8A-20A for CA_8A-20A | VODAFONE Group Plc |
| R4-2104649 | TP for TR 36.717-02-02 to add UL configuration CA_8A-28A for CA_8A-28A | VODAFONE Group Plc |
| R4-2105226 | TP for TR 36.717-02-02 to add UL configuration CA_8A-28A for CA_8A-28A | Vodafone |
| 10.5.1 | Rapporteur Input (WID/TR/CR) | |
| R4-2104962 | TR 36.717-03-02 v0.3.0 TR update for LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 | LG Electronics France |
| R4-2104964 | Revised WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 | LG Electronics France |
| 10.5.2 | UE RF with MSD | |
| R4-2105157 | TP for TR 36.717-03-02: to add UL configuration CA_1A-8A for CA_1A-8A-20A-38A | Huawei,HiSilicon |
| R4-2105162 | TP for TR 36.717-03-02: to add UL configuration CA_3A-8A for CA_3A-8A-20A and CA_3C-8A-20A | Huawei,HiSilicon |
| R4-2105231 | TP for TR 36.717-03-02 to add UL configuration CA_3A-8A for CA_3A-8A-20A and CA_3C-8A-20A | Huawei, HiSilicon |
| 10.5.3 | UE RF without MSD | |
| R4-2104963 | TP on summary of self-interference analysis for new x bands (x=3,4,5) DL with 2 bands UL CA | LG Electronics France |
| R4-2105144 | Draft CR to 36.101 to add UL configuration CA_1A-3A for CA_1A-3C-20A | Huawei,HiSilicon |
| R4-2105145 | Draft CR to 36.101 to add UL configuration CA_1A-3A,CA_1A-8A and CA_3A-8A for CA_1A-3C-8A-20A | Huawei,HiSilicon |
| R4-2105146 | Draft CR to 36.101 to add UL configuration CA_1A-8A and CA_3A-8A for CA_1A-3C-7A-8A | Huawei,HiSilicon |
| R4-2105147 | TP for TR 36.717-03-02: to add UL configuration CA_1A-3A for CA_1A-3A-20A-38A and CA_1A-3C-20A-38A | Huawei,HiSilicon |
| R4-2105148 | TP for TR 36.717-03-02: to add UL configuration CA_1A-3A for CA_1A-3A-7A-38A | Huawei,HiSilicon |
| R4-2105149 | TP for TR 36.717-03-02: to add UL configuration CA_1A-3A for CA_1A-3A-7A-8A-38A | Huawei,HiSilicon |
| R4-2105150 | TP for TR 36.717-03-02: to add UL configuration CA_1A-3A for CA_1A-3A-8A-20A and CA_1A-3C-8A-20A | Huawei,HiSilicon |
| R4-2105151 | TP for TR 36.717-03-02: to add UL configuration CA_1A-3A for CA_1A-3A-8A-20A-38A | Huawei,HiSilicon |
| R4-2105152 | TP for TR 36.717-03-02: to add UL configuration CA_1A-8A for CA_1A-3A-7A-8A-38A | Huawei,HiSilicon |
| R4-2105153 | TP for TR 36.717-03-02: to add UL configuration CA_1A-8A for CA_1A-3A-8A-20A and CA_1A-3C-8A-20A | Huawei,HiSilicon |
| R4-2105154 | TP for TR 36.717-03-02: to add UL configuration CA_1A-8A for CA_1A-3A-8A-20A-38A | Huawei,HiSilicon |
| R4-2105155 | TP for TR 36.717-03-02: to add UL configuration CA_1A-8A for CA_1A-7A-8A-38A | Huawei,HiSilicon |
| R4-2105156 | TP for TR 36.717-03-02: to add UL configuration CA_1A-8A for CA_1A-8A-20A | Huawei,HiSilicon |
| R4-2105158 | TP for TR 36.717-03-02: to add UL configuration CA_3A-8A for CA_1A-3A-7A-8A-38A | Huawei,HiSilicon |
| R4-2105159 | TP for TR 36.717-03-02: to add UL configuration CA_3A-8A for CA_1A-3A-8A-20A and CA_1A-3C-8A-20A | Huawei,HiSilicon |
| R4-2105160 | TP for TR 36.717-03-02: to add UL configuration CA_3A-8A for CA_1A-3A-8A-20A-38A | Huawei,HiSilicon |
| R4-2105161 | TP for TR 36.717-03-02: to add UL configuration CA_3A-8A for CA_3A-7A-8A-38A | Huawei,HiSilicon |
| R4-2105163 | TP for TR 36.717-03-02: to add UL configuration CA_3A-8A for CA_3A-8A-20A-38A | Huawei,HiSilicon |
| R4-2105227 | TP for TR 36.717-03-02: to add UL configuration CA_1A-3A for CA_1A-3A-7A-8A-38A | Huawei,HiSilicon |
| R4-2105228 | TP for TR 36.717-03-02: to add UL configuration CA_1A-3A for CA_1A-3A-8A-20A and CA_1A-3C-8A-20A | Huawei,HiSilicon |
| R4-2105229 | TP for TR 36.717-03-02: to add UL configuration CA_1A-3A for CA_1A-3A-8A-20A-38A | Huawei,HiSilicon |
| R4-2105230 | TP for TR 36.717-03-02 to add UL configuration CA_1A-8A for CA_1A-8A-20A | Huawei, HiSilicon |
| R4-2105232 | TP for TR 36.717-03-02_CA_1A-3A-7A-20A-38A | ZTE Corporation |
| R4-2105233 | TP for TR 36.717-03-02_CA_1A-3A-20A-38A | ZTE Corporation |
| R4-2105234 | TP for TR 36.717-03-02_CA_3A-7A-20A-38A | ZTE Corporation |
| R4-2105971 | Draft CR to 36.101 to add UL configuration CA_1A-8A and CA_3A-8A for CA_1A-3C-8A-38A | Huawei,HiSilicon |
| R4-2106375 | TP for TR 36.717-03-02_CA_1A-3A-7A-20A-38A | ZTE Corporation |
| R4-2106376 | TP for TR 36.717-03-02_CA_1A-3A-20A-38A | ZTE Corporation |
| R4-2106377 | TP for TR 36.717-03-02_CA_3A-7A-20A-38A | ZTE Corporation |
| 10.7 | New WID on Additional LTE bands for UE category M1&M2 and/or NB1&NB2 in Rel-17 | |
| R4-2105219 | Email discussion summary for [98-bis-e][146] LTE_bands_R17_M1_M2_NB1_NB2 | Moderator (Ericsson) |
| 10.7.2 | RF | |
| R4-2107247 | On B24 A-MPR for CAT-M1/M2 | Ericsson |
| 10.9 | Additional enhancements for NB-IoT and LTE-MTC | |
| R4-2105220 | Email discussion summary for [98-bis-e][147] Additional enhancements for NB-IoT and LTE-MTC | Huawei |
| R4-2105432 | Way forward on BS RF requirements for R17 NB-IoT 16QAM | Huawei, HiSilicon, Ericsson |
| R4-2105433 | Way forward on UE RF requirements for R17 NB-IoT 16QAM | Nokia |
| R4-2105482 | Email discussion summary for [98-bis-e][147] NB_IOTenh4_LTE_eMTC6 | Moderator (Huawei) |
| 10.9.1 | General and work plan | |
| R4-2107255 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei, HiSilicon, Ericsson |
| 10.9.2.1 | BS RF requirements | |
| R4-2104458 | Proposals on BS RF requirements for support of 16QAM in NB-IoT | Nokia, Nokia Shanghai Bell |
| R4-2107245 | BS RF impact analysis on R17 NB_IoT | Ericsson |
| 10.9.2.2 | UE RF requirements | |
| R4-2104651 | MPR for NB-IoT 16-QAM | Nokia Corporation |
| R4-2107246 | UE RF impact analysis on R17 NB_IoT | Ericsson |
| R4-2107258 | MPR Simulation Assumptions for 16QAM NB-IoT Uplink | Huawei, HiSilicon |
| 10.9.3.1 | UE RF requirements | |
| R4-2107244 | RF impact analysis on Rel-17 eMTC WID | Ericsson |
| 11.1 | High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands 5 and 12 and NR band n71 | |
| R4-2105221 | Email discussion summary for [98-bis-e][148] FS_LTE_NR_HPUE_FWVM | Man Hung Ng (Nokia) |
| R4-2105483 | Email discussion summary for [98-bis-e][148] FS_LTE_NR_HPUE_FWVM | Moderator (Nokia) |
| 11.1.1 | General | |
| R4-2104459 | TR 37.880 V1.0.0: High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71 | Nokia, Nokia Shanghai Bell |
| 11.1.2 | Coexistence study | |
| R4-2104460 | TP to TR 37.880: Coexistence Simulation Results for High-power UE Vs NB-IoT in-band operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71 | Nokia, Nokia Shanghai Bell |
| R4-2105434 | TP to TR 37.880: Coexistence Simulation Results for High-power UE Vs NB-IoT in-band operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71 | Nokia, Nokia Shanghai Bell |
| 11.1.3 | UE RF | |
| R4-2104461 | TP to TR 37.880: BS receiver blocking for High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71 | Nokia, Nokia Shanghai Bell |
| 12 | Liaison and output to other groups | |
| R4-2104705 | Draft LS reply on simultaneous Rx/Tx capability | Qualcomm Incorporated |
| 12.1 | R17 related | |
| R4-2104428 | On temporary RS for efficient SCell activation | ZTE Corporation |
| R4-2104429 | Reply LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state | ZTE Corporation |
| R4-2104542 | Discussion and reply LS on Half-duplex FDD switching time for RedCap UE | vivo |
| R4-2104563 | Beam switching gaps for Multi-TRP UL transmission | Nokia Japan |
| R4-2104567 | Reply LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | MediaTek inc. |
| R4-2104609 | Discussion and draft LS on UE transmit timing error | CMCC |
| R4-2104631 | Considerations on temporary RS for efficient SCell activation in NR CA | vivo |
| R4-2104648 | Discussion on the reply to LS on UE transmit timing error | MediaTek Inc. |
| R4-2104702 | UE configuration for enhanced Joint Channel Estimation in TDD | Sony |
| R4-2104703 | Discussion on LS on questions to RAN WGs on dual Radio UE (2Rx/2Tx or 2Rx/1Tx) support for simultaneous communication with both SNPN and PLMN | Sony |
| R4-2104708 | Discussion on UE transmit timing error | Nokia Corporation |
| R4-2104725 | Discussion on UE transmit timing error | Nokia, Nokia Shanghai Bell |
| R4-2104767 | Discussion on UE transmit timing error | CATT |
| R4-2104768 | Response LS on UE transmit timing error | CATT |
| R4-2104822 | On UE Tx transmit timing error and the reply LS | ZTE Wistron Telecom AB |
| R4-2104848 | Discussion on reply LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Apple |
| R4-2104853 | Discussion on RAN1 LS on UE transmit timing error for R17 URLLC | Apple |
| R4-2104984 | Discussion for reply LS of UE transmit timing error | NEC |
| R4-2105222 | Email discussion summary for [98-bis-e][149] NR_reply_LS_Part_1 | Moderator (Ericsson) |
| R4-2105223 | Email discussion summary for [98-bis-e] [150] NR_reply_LS_Part_2 | Moderator (Samsung) |
| R4-2105332 | LS on questions to RAN WGs on dual Radio UE (2Rx/2Tx or 2Rx/1Tx) support for simultaneous communication with both SNPN and PLMN | Sony |
| R4-2105435 | Way forward on transition time for Type A HD-FDD UE | Ericsson |
| R4-2105436 | [draft]Second reply LS on Beam switching gaps for Multi-TRP UL transmission | Nokia |
| R4-2105437 | Reply LS On minimum requirements for Transmit ON/OFF time mask in UL MIMO FR1 | vivo |
| R4-2105438 | Way forward on exception requirements for Intermodulation due to Dual uplink (IMD) | Xiaomi |
| R4-2105484 | Email discussion summary for [98-bis-e][149] NR_reply_LS_Part_1 | Moderator (Ericsson) |
| R4-2105485 | Email discussion summary for [98-bis-e][150] NR_reply_LS_Part_2 | Moderator (Samsung |
| R4-2105486 | Email discussion summary for [98-bis-e][151] NR_reply_LS_Part_3 | Moderator (Xiaomi) |
| R4-2105695 | Email discussion summary: [98-bis-e][225] LS_reply_R1-2009798_MR_DC_NWM | Moderator (Huawei) |
| R4-2105696 | Email discussion summary for [98-bis-e][226] LS_reply_R2-2102165_NBIOT | Moderator (Huawei) |
| R4-2105697 | Email discussion summary for [98-bis-e][227] LS_reply_R1-2102245_IIoT_URLLC | Moderator (Nokia) |
| R4-2105698 | Email discussion summary: [98-bis-e][228] LS_reply_R1-2102248_feMIMO | Moderator (Samsung) |
| R4-2105798 | WF on Temporary RS for efficient SCell activation | Huawei, HiSilicon |
| R4-2105799 | Reply LS on temporary RS for efficient SCell activation in NR CA | Huawei, HiSilicon |
| R4-2105800 | Reply LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state | Huawei, HiSilicon |
| R4-2105801 | WF on neighbour cell measurement in NB-IoT RRC_CONNECTED state in Rel-17 | Ericsson |
| R4-2105802 | Reply LS on UE transmit timing error | Huawei |
| R4-2105825 | Email discussion summary: [98-bis-e][225] LS_reply_R1-2009798_MR_DC_NWM | Moderator (Huawei) |
| R4-2105826 | Email discussion summary: [98-bis-e][226] LS_reply_R2-2102165_NBIOT | Moderator (Huawei) |
| R4-2105827 | Email discussion summary: [98-bis-e][227] LS_reply_R1-2102245_IIoT_URLLC | Moderator (Nokia) |
| R4-2105828 | Email discussion summary: [98-bis-e][228] LS_reply_R1-2102248_feMIMO | Moderator (Samsung) |
| R4-2105838 | WF on feMIMO on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Samsung |
| R4-2105849 | WF on neighbour cell measurement in NB-IoT RRC_CONNECTED state in Rel-17 | Ericsson |
| R4-2105850 | Reply LS on UE transmit timing error | Huawei |
| R4-2106345 | Discussion of neighbor cell measurements in RRC_CONNECTED for Rel-17 NB-IoT | Qualcomm Incorporated |
| R4-2106398 | Discussion on incoming L1/L2 mobility LS. | Nokia, Nokia Shanghai Bell |
| R4-2106443 | Discussion on temporary RS for efficient Scell activation | Intel Corporation |
| R4-2106445 | Reply to LS on UE transmit timing error | Intel Corporation |
| R4-2106671 | Discussion and draft Reply LS on Half-duplex FDD switching time for RedCap UE | Huawei, HiSilicon |
| R4-2106776 | draft LS reply to R5-211609 about IMD exceptions | Ericsson |
| R4-2106857 | Reply LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state | Ericsson |
| R4-2106878 | Reply LS on TCI State Update for L1/L2 Centric Inter-Cell Mobility | Ericsson |
| R4-2106887 | Temporary RS for Scell activation delay reduction | Ericsson |
| R4-2106938 | Discussion on temporary RS for efficient SCell activation in NR CA | Huawei, HiSilicon |
| R4-2106941 | Discussion on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Huawei, HiSilicon |
| R4-2106985 | Reply LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state | Huawei, HiSilicon |
| R4-2107031 | reply LS on UE transmit timing error | Huawei, HiSilicon |
| R4-2107086 | Discussion on LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | vivo |
| R4-2107125 | Discussion on temporary RS | MediaTek inc. |
| R4-2107153 | LS response on UE transmit timing error | Ericsson |
| R4-2107185 | Discussion on neighbour cell measurements in NB-IoT RRC_CONNECTED state | Nokia, Nokia Shanghai Bell |
| R4-2107186 | Discussion on HD-FDD switching times for RedCap UE | Nokia, Nokia Shanghai Bell |
| R4-2107248 | Reply LS to Half-duplex FDD switching for RedCap UE | Ericsson |
| R4-2107340 | Type-A Half-duplex FDD switching time for RedCap UE | Qualcomm Incorporated |
| R4-2107364 | Discussion on incoming RAN1 LS for L1/L2 inter-cell mobility and draft LS out | Qualcomm CDMA Technologies |
| 12.2 | Others | |
| R4-2104402 | RAN2 LS on addition of 400 and 600 MHz Fs | Nokia, Nokia Shanghai Bell |
| R4-2104520 | Discussion and reply LS on Clarification on exception requirements for Intermodulation due to Dual uplink (IMD) | vivo |
| R4-2104543 | Discussion and reply LS On minimum requirements for Transmit ON/OFF time mask in UL MIMO FR1 | vivo |
| R4-2104894 | Discussion and draft reply LS on simultaneous Rx/Tx capability | Apple |
| R4-2105224 | Email discussion summary for [98-bis-e][151] NR_reply_LS_Part_3 | Moderator (Xiaomi) |
| R4-2105999 | Email discussion summary for [98-bis-e][328] LS_reply_ITU-R | Moderator (Ericsson) |
| R4-2106125 | WF on OTA in-field testing and antenna model information to ITU-R | Ericsson |
| R4-2106159 | Email discussion summary for [98-bis-e][328] LS_reply_ITU-R | Moderator (Ericsson) |
| R4-2106354 | Draft LS to ITU-R and CEPT on extension of IMT array antenna model to support sub-array structures | Ericsson, Nokia, Qualcomm |
| R4-2106356 | Draft LS on feedback on LS from ITU-R WP 1C related to in-field unwanted emission testing | Ericsson |
| R4-2106551 | Discussion on reply LS on Clarification on exception requirements for Intermodulation due to Dual uplink (IMD) | Xiaomi |
| R4-2106552 | Discussion on Frequency Bands for testing of A-GNSS Sensitivity requirements in NR and LTE | Xiaomi |
| 13.1.1 | Spectrum related | |
| R4-2104484 | Co-existence challenges with NR-U 100MHz channel bandwidth and other technologies | Charter Communications, Inc |
| R4-2104494 | NR-U Punctured Channel SEM for 100 MHz Bandwidth | CableLabs |
| R4-2104884 | Supporting the 6GHz band in other countries/regions | Apple |
| R4-2105021 | Motivation for new WI on air-to-ground network for NR | CMCC |
| R4-2105022 | New WID on air-to-ground network for NR | CMCC |
| 14 | Any other business | |
| R4-2104496 | Draft CR to TS 38.104: Additional of FCC emission limits on US 3.45-3.55 GHz band | Nokia, Nokia Shanghai Bell |
| R4-2104497 | Draft CR to TS 38.104: Additional of FCC emission limits on US 3.45-3.55 GHz band | Nokia, Nokia Shanghai Bell |
| R4-2105225 | Email discussion summary for [98-bis-e][152] US_n77 | Moderator (Apple) |
| R4-2105439 | Way forward on Enabling US 3.45 – 3.55GHz in Band n77 | Apple |
| R4-2105487 | Email discussion summary for [98-bis-e][152] US_n77 | Moderator (Apple) |
| R4-2107109 | Band n77 usage in the US for 3.45 to 3.55 GHz | Apple |
| R4-2107330 | NB-IoT Testing | T-Mobile USA, Qualcomm |
| R4-2107349 | Enabling US 3.45 – 3.55 GHz with Band n77 | Qualcomm Incorporated, AT&T |
| R4-2107350 | Addition of new spectrum in Band n77 for US | Qualcomm Incorporated, AT&T, Nokia |
| 15 | Close of the E-meeting | |
| R4-2105106 | Incoming LSs | ETSI MCC |
| R4-2105107 | Incoming LSs | ETSI MCC |
| R4-2105108 | Incoming LSs | ETSI MCC |
| R4-2105109 | Incoming LSs | ETSI MCC |
| R4-2105110 | Incoming LSs | ETSI MCC |
| R4-2105111 | Incoming LSs | ETSI MCC |
| R4-2105112 | Incoming LSs | ETSI MCC |
| R4-2105113 | Incoming LSs | ETSI MCC |
| R4-2105114 | Incoming LSs | ETSI MCC |
| R4-2105115 | Incoming LSs | ETSI MCC |
| R4-2105116 | Incoming LSs | ETSI MCC |
| R4-2105117 | Incoming LSs | ETSI MCC |
| R4-2105118 | Incoming LSs | ETSI MCC |
| R4-2105119 | Incoming LSs | ETSI MCC |
| R4-2105120 | Incoming LSs | ETSI MCC |
| R4-2105121 | Incoming LSs | ETSI MCC |
| R4-2105122 | Incoming LSs | ETSI MCC |
| R4-2105123 | Incoming LSs | ETSI MCC |
| R4-2105124 | Incoming LSs | ETSI MCC |
| R4-2105125 | Incoming LSs | ETSI MCC |
| R4-2105126 | Incoming LSs | ETSI MCC |
| R4-2105127 | Incoming LSs | ETSI MCC |
| R4-2105128 | Incoming LSs | ETSI MCC |
| R4-2105129 | Incoming LSs | ETSI MCC |
| R4-2105130 | Incoming LSs | ETSI MCC |
| R4-2105131 | Incoming LSs | ETSI MCC |
| R4-2105132 | Incoming LSs | ETSI MCC |
| R4-2105133 | Incoming LSs | ETSI MCC |
| R4-2105134 | Incoming LSs | ETSI MCC |
| R4-2105135 | Incoming LSs | ETSI MCC |
| R4-2105136 | Incoming LSs | ETSI MCC |
| R4-2105244 | (reserved) | Main Session |
| R4-2105409 | (reserved) | Main Session |
| R4-2105428 | (reserved) | Main Session |
| R4-2105429 | (reserved) | Main Session |
| R4-2105498 | (reserved) | Main Session |
| R4-2105499 | (reserved) | Main Session |
| R4-2105500 | (reserved) | Main Session |
| R4-2105501 | (reserved) | Main Session |
| R4-2105502 | (reserved) | Main Session |
| R4-2105503 | (reserved) | Main Session |
| R4-2105504 | (reserved) | Main Session |
| R4-2105505 | (reserved) | Main Session |
| R4-2105506 | (reserved) | Main Session |
| R4-2105507 | (reserved) | Main Session |
| R4-2105508 | (reserved) | Main Session |
| R4-2105509 | (reserved) | Main Session |
| R4-2105510 | (reserved) | Main Session |
| R4-2105511 | (reserved) | Main Session |
| R4-2105512 | (reserved) | Main Session |
| R4-2105513 | (reserved) | Main Session |
| R4-2105514 | (reserved) | Main Session |
| R4-2105515 | (reserved) | Main Session |
| R4-2105516 | (reserved) | Main Session |
| R4-2105517 | (reserved) | Main Session |
| R4-2105518 | (reserved) | Main Session |
| R4-2105519 | (reserved) | Main Session |
| R4-2105520 | (reserved) | Main Session |
| R4-2105521 | (reserved) | Main Session |
| R4-2105522 | (reserved) | Main Session |
| R4-2105523 | (reserved) | Main Session |
| R4-2105524 | (reserved) | Main Session |
| R4-2105525 | (reserved) | Main Session |
| R4-2105526 | (reserved) | Main Session |
| R4-2105527 | (reserved) | Main Session |
| R4-2105528 | (reserved) | Main Session |
| R4-2105529 | (reserved) | Main Session |
| R4-2105530 | (reserved) | Main Session |
| R4-2105531 | (reserved) | Main Session |
| R4-2105532 | (reserved) | Main Session |
| R4-2105533 | (reserved) | Main Session |
| R4-2105534 | (reserved) | Main Session |
| R4-2105535 | (reserved) | Main Session |
| R4-2105536 | (reserved) | Main Session |
| R4-2105537 | (reserved) | Main Session |
| R4-2105538 | (reserved) | Main Session |
| R4-2105539 | (reserved) | Main Session |
| R4-2105540 | (reserved) | Main Session |
| R4-2105541 | (reserved) | Main Session |
| R4-2105542 | (reserved) | Main Session |
| R4-2105543 | (reserved) | Main Session |
| R4-2105544 | (reserved) | Main Session |
| R4-2105545 | (reserved) | Main Session |
| R4-2105546 | (reserved) | Main Session |
| R4-2105547 | (reserved) | Main Session |
| R4-2105548 | (reserved) | Main Session |
| R4-2105549 | (reserved) | Main Session |
| R4-2105550 | (reserved) | Main Session |
| R4-2105551 | (reserved) | Main Session |
| R4-2105552 | (reserved) | Main Session |
| R4-2105553 | (reserved) | Main Session |
| R4-2105554 | (reserved) | Main Session |
| R4-2105555 | (reserved) | Main Session |
| R4-2105556 | (reserved) | Main Session |
| R4-2105557 | (reserved) | Main Session |
| R4-2105558 | (reserved) | Main Session |
| R4-2105559 | (reserved) | Main Session |
| R4-2105560 | (reserved) | Main Session |
| R4-2105561 | (reserved) | Main Session |
| R4-2105562 | (reserved) | Main Session |
| R4-2105563 | (reserved) | Main Session |
| R4-2105564 | (reserved) | Main Session |
| R4-2105565 | (reserved) | Main Session |
| R4-2105566 | (reserved) | Main Session |
| R4-2105567 | (reserved) | Main Session |
| R4-2105568 | (reserved) | Main Session |
| R4-2105569 | (reserved) | Main Session |
| R4-2105570 | (reserved) | Main Session |
| R4-2105571 | (reserved) | Main Session |
| R4-2105572 | (reserved) | Main Session |
| R4-2105573 | (reserved) | Main Session |
| R4-2105574 | (reserved) | Main Session |
| R4-2105575 | (reserved) | Main Session |
| R4-2105576 | (reserved) | Main Session |
| R4-2105577 | (reserved) | Main Session |
| R4-2105578 | (reserved) | Main Session |
| R4-2105579 | (reserved) | Main Session |
| R4-2105580 | (reserved) | Main Session |
| R4-2105581 | (reserved) | Main Session |
| R4-2105582 | (reserved) | Main Session |
| R4-2105583 | (reserved) | Main Session |
| R4-2105584 | (reserved) | Main Session |
| R4-2105585 | (reserved) | Main Session |
| R4-2105586 | (reserved) | Main Session |
| R4-2105587 | (reserved) | Main Session |
| R4-2105588 | (reserved) | Main Session |
| R4-2105589 | (reserved) | Main Session |
| R4-2105590 | (reserved) | Main Session |
| R4-2105591 | (reserved) | Main Session |
| R4-2105592 | (reserved) | Main Session |
| R4-2105593 | (reserved) | Main Session |
| R4-2105594 | (reserved) | Main Session |
| R4-2105595 | (reserved) | Main Session |
| R4-2105596 | (reserved) | Main Session |
| R4-2105597 | (reserved) | Main Session |
| R4-2105598 | (reserved) | Main Session |
| R4-2105599 | (reserved) | Main Session |
| R4-2105600 | (reserved) | Main Session |
| R4-2105601 | (reserved) | Main Session |
| R4-2105602 | (reserved) | Main Session |
| R4-2105603 | (reserved) | Main Session |
| R4-2105604 | (reserved) | Main Session |
| R4-2105605 | (reserved) | Main Session |
| R4-2105606 | (reserved) | Main Session |
| R4-2105607 | (reserved) | Main Session |
| R4-2105608 | (reserved) | Main Session |
| R4-2105609 | (reserved) | Main Session |
| R4-2105610 | (reserved) | Main Session |
| R4-2105611 | (reserved) | Main Session |
| R4-2105612 | (reserved) | Main Session |
| R4-2105613 | (reserved) | Main Session |
| R4-2105614 | (reserved) | Main Session |
| R4-2105615 | (reserved) | Main Session |
| R4-2105616 | (reserved) | Main Session |
| R4-2105617 | (reserved) | Main Session |
| R4-2105618 | (reserved) | Main Session |
| R4-2105619 | (reserved) | Main Session |
| R4-2105620 | (reserved) | Main Session |
| R4-2105621 | (reserved) | Main Session |
| R4-2105622 | (reserved) | Main Session |
| R4-2105623 | (reserved) | Main Session |
| R4-2105624 | (reserved) | Main Session |
| R4-2105625 | (reserved) | Main Session |
| R4-2105626 | (reserved) | Main Session |
| R4-2105627 | (reserved) | Main Session |
| R4-2105628 | (reserved) | Main Session |
| R4-2105629 | (reserved) | Main Session |
| R4-2105630 | (reserved) | Main Session |
| R4-2105631 | (reserved) | Main Session |
| R4-2105632 | (reserved) | Main Session |
| R4-2105633 | (reserved) | Main Session |
| R4-2105634 | (reserved) | Main Session |
| R4-2105635 | (reserved) | Main Session |
| R4-2105636 | (reserved) | Main Session |
| R4-2105637 | (reserved) | Main Session |
| R4-2105638 | (reserved) | Main Session |
| R4-2105639 | (reserved) | Main Session |
| R4-2105640 | (reserved) | Main Session |
| R4-2105641 | (reserved) | Main Session |
| R4-2105642 | (reserved) | Main Session |
| R4-2105643 | (reserved) | Main Session |
| R4-2105644 | (reserved) | Main Session |
| R4-2105645 | (reserved) | Main Session |
| R4-2105646 | (reserved) | Main Session |
| R4-2105647 | (reserved) | Main Session |
| R4-2105648 | (reserved) | Main Session |
| R4-2105649 | (reserved) | Main Session |
| R4-2105650 | (reserved) | Main Session |
| R4-2105651 | (reserved) | Main Session |
| R4-2105652 | (reserved) | Main Session |
| R4-2105653 | (reserved) | Main Session |
| R4-2105654 | (reserved) | Main Session |
| R4-2105655 | (reserved) | Main Session |
| R4-2105656 | (reserved) | Main Session |
| R4-2105657 | (reserved) | Main Session |
| R4-2105658 | (reserved) | Main Session |
| R4-2105659 | (reserved) | Main Session |
| R4-2105660 | (reserved) | Main Session |
| R4-2105661 | (reserved) | Main Session |
| R4-2105662 | (reserved) | Main Session |
| R4-2105663 | (reserved) | Main Session |
| R4-2105664 | (reserved) | Main Session |
| R4-2105665 | (reserved) | Main Session |
| R4-2105666 | (reserved) | Main Session |
| R4-2105667 | (reserved) | Main Session |
| R4-2105668 | (reserved) | Main Session |
| R4-2105669 | (reserved) | Main Session |
| R4-2105670 | (reserved) | Main Session |
| R4-2105713 | Draft CR on DL CCA model for NR-U | Nokia, Nokia Shanghai Bell, Ericsson |
| R4-2105839 | Thank Steven for RAN4 Leadership | Source: All of us |
| R4-2105859 | Thank Steven for RAN4 Leadership | Source: All of us |
| R4-2105860 | (reserved) | RRM Session |
| R4-2105861 | (reserved) | RRM Session |
| R4-2105862 | (reserved) | RRM Session |
| R4-2105863 | (reserved) | RRM Session |
| R4-2105864 | (reserved) | RRM Session |
| R4-2105865 | (reserved) | RRM Session |
| R4-2105866 | (reserved) | RRM Session |
| R4-2105867 | (reserved) | RRM Session |
| R4-2105868 | (reserved) | RRM Session |
| R4-2105869 | (reserved) | RRM Session |
| R4-2105870 | (reserved) | RRM Session |
| R4-2105871 | (reserved) | RRM Session |
| R4-2105872 | (reserved) | RRM Session |
| R4-2105873 | (reserved) | RRM Session |
| R4-2105874 | (reserved) | RRM Session |
| R4-2105875 | (reserved) | RRM Session |
| R4-2105876 | (reserved) | RRM Session |
| R4-2105877 | (reserved) | RRM Session |
| R4-2105878 | (reserved) | RRM Session |
| R4-2105879 | (reserved) | RRM Session |
| R4-2105880 | (reserved) | RRM Session |
| R4-2105881 | (reserved) | RRM Session |
| R4-2105882 | (reserved) | RRM Session |
| R4-2105883 | (reserved) | RRM Session |
| R4-2105884 | (reserved) | RRM Session |
| R4-2105885 | (reserved) | RRM Session |
| R4-2105886 | (reserved) | RRM Session |
| R4-2105887 | (reserved) | RRM Session |
| R4-2105888 | (reserved) | RRM Session |
| R4-2105889 | (reserved) | RRM Session |
| R4-2105890 | (reserved) | RRM Session |
| R4-2105891 | (reserved) | RRM Session |
| R4-2105892 | (reserved) | RRM Session |
| R4-2105893 | (reserved) | RRM Session |
| R4-2105894 | (reserved) | RRM Session |
| R4-2105895 | (reserved) | RRM Session |
| R4-2105896 | (reserved) | RRM Session |
| R4-2105897 | (reserved) | RRM Session |
| R4-2105898 | (reserved) | RRM Session |
| R4-2105899 | (reserved) | RRM Session |
| R4-2105900 | (reserved) | RRM Session |
| R4-2105901 | (reserved) | RRM Session |
| R4-2105902 | (reserved) | RRM Session |
| R4-2105903 | (reserved) | RRM Session |
| R4-2105904 | (reserved) | RRM Session |
| R4-2105905 | (reserved) | RRM Session |
| R4-2105906 | (reserved) | RRM Session |
| R4-2105907 | (reserved) | RRM Session |
| R4-2105908 | (reserved) | RRM Session |
| R4-2105909 | (reserved) | RRM Session |
| R4-2105910 | (reserved) | RRM Session |
| R4-2105911 | (reserved) | RRM Session |
| R4-2105912 | (reserved) | RRM Session |
| R4-2105913 | (reserved) | RRM Session |
| R4-2105914 | (reserved) | RRM Session |
| R4-2105915 | (reserved) | RRM Session |
| R4-2105916 | (reserved) | RRM Session |
| R4-2105917 | (reserved) | RRM Session |
| R4-2105918 | (reserved) | RRM Session |
| R4-2105919 | (reserved) | RRM Session |
| R4-2105920 | (reserved) | RRM Session |
| R4-2105921 | (reserved) | RRM Session |
| R4-2105922 | (reserved) | RRM Session |
| R4-2105923 | (reserved) | RRM Session |
| R4-2105924 | (reserved) | RRM Session |
| R4-2105925 | (reserved) | RRM Session |
| R4-2105926 | (reserved) | RRM Session |
| R4-2105927 | (reserved) | RRM Session |
| R4-2105928 | (reserved) | RRM Session |
| R4-2105929 | (reserved) | RRM Session |
| R4-2105930 | (reserved) | RRM Session |
| R4-2105931 | (reserved) | RRM Session |
| R4-2105932 | (reserved) | RRM Session |
| R4-2105933 | (reserved) | RRM Session |
| R4-2105934 | (reserved) | RRM Session |
| R4-2105935 | (reserved) | RRM Session |
| R4-2105936 | (reserved) | RRM Session |
| R4-2105937 | (reserved) | RRM Session |
| R4-2105938 | (reserved) | RRM Session |
| R4-2105939 | (reserved) | RRM Session |
| R4-2105940 | (reserved) | RRM Session |
| R4-2105941 | (reserved) | RRM Session |
| R4-2105942 | (reserved) | RRM Session |
| R4-2105943 | (reserved) | RRM Session |
| R4-2105944 | (reserved) | RRM Session |
| R4-2105945 | (reserved) | RRM Session |
| R4-2105946 | (reserved) | RRM Session |
| R4-2105947 | (reserved) | RRM Session |
| R4-2105948 | (reserved) | RRM Session |
| R4-2105949 | (reserved) | RRM Session |
| R4-2105950 | (reserved) | RRM Session |
| R4-2105951 | (reserved) | RRM Session |
| R4-2105952 | (reserved) | RRM Session |
| R4-2105953 | (reserved) | RRM Session |
| R4-2105954 | (reserved) | RRM Session |
| R4-2105955 | (reserved) | RRM Session |
| R4-2105956 | (reserved) | RRM Session |
| R4-2105957 | (reserved) | RRM Session |
| R4-2105958 | (reserved) | RRM Session |
| R4-2105959 | (reserved) | RRM Session |
| R4-2105960 | (reserved) | RRM Session |
| R4-2105961 | (reserved) | RRM Session |
| R4-2105962 | (reserved) | RRM Session |
| R4-2105963 | (reserved) | RRM Session |
| R4-2105964 | (reserved) | RRM Session |
| R4-2105965 | (reserved) | RRM Session |
| R4-2105966 | (reserved) | RRM Session |
| R4-2105967 | (reserved) | RRM Session |
| R4-2105968 | (reserved) | RRM Session |
| R4-2105969 | (reserved) | RRM Session |
| R4-2105970 | (reserved) | RRM Session |
| R4-2106006 | (reserved) | BSRF Session |
| R4-2106009 | (reserved) | BSRF Session |
| R4-2106120 | Way forward for FR1 PUSCH 256QAM performance requirements | Huawei |
| R4-2106123 | (reserved) | BSRF Session |
| R4-2106126 | (reserved) | BSRF Session |
| R4-2106169 | (reserved) | BSRF Session |
| R4-2106170 | (reserved) | BSRF Session |
| R4-2106171 | (reserved) | BSRF Session |
| R4-2106175 | (reserved) | BSRF Session |
| R4-2106176 | (reserved) | BSRF Session |
| R4-2106177 | (reserved) | BSRF Session |
| R4-2106178 | (reserved) | BSRF Session |
| R4-2106179 | (reserved) | BSRF Session |
| R4-2106180 | (reserved) | BSRF Session |
| R4-2106181 | (reserved) | BSRF Session |
| R4-2106182 | (reserved) | BSRF Session |
| R4-2106183 | (reserved) | BSRF Session |
| R4-2106184 | (reserved) | BSRF Session |
| R4-2106185 | (reserved) | BSRF Session |
| R4-2106186 | (reserved) | BSRF Session |
| R4-2106187 | (reserved) | BSRF Session |
| R4-2106188 | (reserved) | BSRF Session |
| R4-2106189 | (reserved) | BSRF Session |
| R4-2106190 | (reserved) | BSRF Session |
| R4-2106191 | (reserved) | BSRF Session |
| R4-2106192 | (reserved) | BSRF Session |
| R4-2106193 | (reserved) | BSRF Session |
| R4-2106194 | (reserved) | BSRF Session |
| R4-2106195 | (reserved) | BSRF Session |
| R4-2106196 | (reserved) | BSRF Session |
| R4-2106197 | (reserved) | BSRF Session |
| R4-2106198 | (reserved) | BSRF Session |
| R4-2106199 | (reserved) | BSRF Session |
| R4-2106200 | (reserved) | BSRF Session |
| R4-2106201 | (reserved) | BSRF Session |
| R4-2106202 | (reserved) | BSRF Session |
| R4-2106203 | (reserved) | BSRF Session |
| R4-2106204 | (reserved) | BSRF Session |
| R4-2106205 | (reserved) | BSRF Session |
| R4-2106206 | (reserved) | BSRF Session |
| R4-2106207 | (reserved) | BSRF Session |
| R4-2106208 | (reserved) | BSRF Session |
| R4-2106209 | (reserved) | BSRF Session |
| R4-2106210 | (reserved) | BSRF Session |
| R4-2106211 | (reserved) | BSRF Session |
| R4-2106212 | (reserved) | BSRF Session |
| R4-2106213 | (reserved) | BSRF Session |
| R4-2106214 | (reserved) | BSRF Session |
| R4-2106215 | (reserved) | BSRF Session |
| R4-2106216 | (reserved) | BSRF Session |
| R4-2106217 | (reserved) | BSRF Session |
| R4-2106218 | (reserved) | BSRF Session |
| R4-2106219 | (reserved) | BSRF Session |
| R4-2106220 | (reserved) | BSRF Session |
| R4-2106221 | (reserved) | BSRF Session |
| R4-2106222 | (reserved) | BSRF Session |
| R4-2106223 | (reserved) | BSRF Session |
| R4-2106224 | (reserved) | BSRF Session |
| R4-2106225 | (reserved) | BSRF Session |
| R4-2106226 | (reserved) | BSRF Session |
| R4-2106227 | (reserved) | BSRF Session |
| R4-2106228 | (reserved) | BSRF Session |
| R4-2106229 | (reserved) | BSRF Session |
| R4-2106230 | (reserved) | BSRF Session |
| R4-2106231 | (reserved) | BSRF Session |
| R4-2106232 | (reserved) | BSRF Session |
| R4-2106233 | (reserved) | BSRF Session |
| R4-2106234 | (reserved) | BSRF Session |
| R4-2106235 | (reserved) | BSRF Session |
| R4-2106236 | (reserved) | BSRF Session |
| R4-2106237 | (reserved) | BSRF Session |
| R4-2106238 | (reserved) | BSRF Session |
| R4-2106239 | (reserved) | BSRF Session |
| R4-2106240 | (reserved) | BSRF Session |
| R4-2106241 | (reserved) | BSRF Session |
| R4-2106242 | (reserved) | BSRF Session |
| R4-2106243 | (reserved) | BSRF Session |
| R4-2106244 | (reserved) | BSRF Session |
| R4-2106245 | (reserved) | BSRF Session |
| R4-2106246 | (reserved) | BSRF Session |
| R4-2106247 | (reserved) | BSRF Session |
| R4-2106248 | (reserved) | BSRF Session |
| R4-2106249 | (reserved) | BSRF Session |
| R4-2106250 | (reserved) | BSRF Session |
| R4-2106251 | (reserved) | BSRF Session |
| R4-2106252 | (reserved) | BSRF Session |
| R4-2106253 | (reserved) | BSRF Session |
| R4-2106254 | (reserved) | BSRF Session |
| R4-2106255 | (reserved) | BSRF Session |
| R4-2106256 | (reserved) | BSRF Session |
| R4-2106257 | (reserved) | BSRF Session |
| R4-2106258 | (reserved) | BSRF Session |
| R4-2106259 | (reserved) | BSRF Session |
| R4-2106260 | (reserved) | BSRF Session |
| R4-2106261 | (reserved) | BSRF Session |
| R4-2106262 | (reserved) | BSRF Session |
| R4-2106263 | (reserved) | BSRF Session |
| R4-2106264 | (reserved) | BSRF Session |
| R4-2106265 | (reserved) | BSRF Session |
| R4-2106266 | (reserved) | BSRF Session |
| R4-2106267 | (reserved) | BSRF Session |
| R4-2106268 | (reserved) | BSRF Session |
| R4-2106269 | (reserved) | BSRF Session |
| R4-2106270 | (reserved) | BSRF Session |
| R4-2106271 | (reserved) | BSRF Session |